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.
The 140byt.es site hasn't launched yet, but for now 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. It was inspired by work from Thomas Fuchs and Dustin Diaz.

Worked on the classic game of life and got a 92 byte result with the same functionality as previous iterations, as well as a 118 byte result with wrapping issues fixed, which can be seen here: http://output.jsbin.com/zebuxi
I decided to use arrow functions when I noticed they were implemented on chrome and firefox, which saved quite a few bytes in combination with Array.prototype.map. I also implemented a flattened walk loop instead of a precalculated walk as most other implementations I've seen, which saved bytes even without the arrow functions.
I encourage you to check out the javascript as I wrote it because I left a history of changes by copy pasting into a new line every iteration: http://jsbin.com/zebuxi/edit?js
Thanks to @aemkei I've really enjoyed reading the code you've written for 140bytes and on your website, a real inspiration.