A tweet-sized, fork-to-play, community-curated collection of JavaScript.
- Click the button above to fork this gist.
- Modify all the files to according to the rules below.
- Save your entry and tweet it up!
Keep in mind that thanks to the awesome sensibilities of the GitHub team, gists are just repos. So feel free to clone yours and work locally for a more comfortable environment, and to allow commit messages.
All entries must exist in an index.js
file, whose contents are
- an assignable, valid Javascript expression that
- contains no more than 140 bytes, and
- does not leak to the global scope.
All entries must also be licensed under the WTFPL or equally permissive license.
See the 140byt.es site for a showcase of entries (built itself using 140-byte entries!), and follow @140bytes on Twitter.
To learn about byte-saving hacks for your own code, or to contribute what you've learned, head to the wiki.
140byt.es is brought to you by Jed Schmidt, with help from Alex Kloss. It was inspired by work from Thomas Fuchs and Dustin Diaz.
Yeah, I'm new to this, but I have a bunch of ideas... I think a link to 140byt.es should be included in the tweets, because it gives some coherence to the tweeting, which are now totally random disconnected fragments of javascript that no one other than 140bytes participants will know what they're about or more importantly, where to go to find out what they're about. Yet, there are lots of js/es programmers out there that would be interested in this if they saw an entry tweet and were able to follow a link to the home page.
That's my argument, now the technical challenge: No matter what the size of a URI/URL twitter now minifies (or expands) it to 22 chars, allowing only 118 remaining for the actual code. I kind of think this is acceptable, because this 1) only make the challenge harder, which is the point, right, hardness? and 2) the chars reserved for the link can be considered part of the task, as it helps to promote the task(s) as a whole