jedschmidt

Nice, it's been a while.

(Anyone looking to celebrate Ramendan[1] pre-game, let me know.)

[1] http://ramendan.com

for those curious about how this compares:

    [RedisToGo]

    Memory    $  $/MB
    -----------------
    5 MB      0  0.00 <= cheapest
    20 MB     5  0.25 
    100 MB   25  0.25 
    500 MB  110  0.22 
    2 GB    300  0.15 

    [openredis]

    Memory    $  $/MB
    -----------------
    50 MB     8  0.16 
    200 MB   25  0.13 
    500 MB   45  0.09 
    1 GB     85  0.09 <= best value

For those not familiar, 140byt.es is a collaborative code-golfing challenge in JavaScript. The objective is to fit as much punch as possible into 140 bytes, and there has been some impressive work from the community.

Examples include 140-byte versions of

  * client-side app helpers: router, jsonp, and templates
  * DOM helpers: selectors, swap, and walk
  * parsers: Base64, roman numerals, URLs, brainfuck
  * math: isPrimeNumber and solveAlgebraicEquation

et cetera. You really have to see some of these entries to believe them. I've learned a lot about JavaScript in the process.

I'd love to see functions too, and am not sure your concerns are necessarily dealbreakers. Optimization should be easier if you use something like node-burrito for the low hanging fruit, and node.js developers are already aware that long synchronous loops should be avoided in a single-threaded environment.

Perhaps something like this would help:

http://imgur.com/gRDGa

And you thought testing your development environment was hard.

http://www.blockedinchina.net/?siteurl=127.0.0.1

This exploits CoffeeScript syntax in the same way that (fab) exploits JavaScript syntax:

https://github.com/jed/fab/blob/browser/demo.html

(I'm biased, but am a fan of making markup "just code".)

This business model has been popular in Japan since cellphones got email:

http://www.cnngo.com/tokyo/play/deaikei-duties-posing-online...

Since those IDs are just the IDs of the tweets underneath, I don't think it has much to do with the elegance of this solution, per se.

Perhaps it would be cleaner use the Flickr approach to set URL naming:

  /<item-id>/in/<set-id>/

I think it makes more sense to have the button match the language of the page content. It would be a bit jarring to see a single Japanese button on an otherwise English page.

Can this API predict when it will be deprecated?

It's also interesting to see how the approaches differ at each order of magnitude from 140byt.es to JS1K to 10K Apart.

At the smallest end you really have to work with what you're given and triage fast, whereas with JS1K you see people writing decompressors _in_ their code to get around JavaScript's occasional verbosity.

Oops, that was an error (the multiplication should be within the .floor call). It's fixed now.

This style of code, while not for everyone, exploits the "happens to be okay" operator precedence. For this, Mozilla's MDC is a great resource:

https://developer.mozilla.org/en/JavaScript/Reference/Operat...

Just remember to fork the master gist (https://gist.github.com/962807) when you're done, and add an annotation so that the rest of us can learn from it!

There's a lot of room in there:

    Math.pow(2,l=a.length)
    1<<(l=a.length)

are the same, as are these:

    if(b[--j]==1)
    ~-b[--j]||

A lot of these tricks _are_ used in production, the result of uglifyjs/closure minification of otherwise sane code. This is just a guide for hand-tuning.

That's already covered, along with use of ~~ for the same purpose.

This is a good point. If you're going to write minified code like this, you should at least annotate it liberally like this example:

https://gist.github.com/962814

For me, step 3 was the overuse of nested closures to store state. More elegant in many ways, but at a significant cost in performance.

The size difference may be more meaningful once the hard dependency of Underscore.js is taken into account.

That said, competing so closely with an Ashkenas library is not a niche I'd want to be in...

This is no longer true as of iOS 4.

can't make it, but will raise a glass of ebisu silk from down here in kyushu.

Very well designed! One thing: out of context in a tab, your favicon could seem inadvertently religious†.

†: http://en.wikipedia.org/wiki/Christian_cross

Facebook is obviously showing only one gender at a time for their social authentication capchas, but I wonder if the correlation between last name and ethnicity is enough to collapse the space of possible answers pretty significantly.

This is already possible with Flickr photos, thanks to flickrtouchr and Dropbox:

    git clone https://github.com/tominsam/flickrtouchr.git
    cd flickrtouchr
    python flickrtouchr.py ~/Dropbox/myphotos

A link would help:

http://www.reuters.com/article/idUSTRE7050YJ20110106

One minor nit: Backbone.js requires Underscore.js (and json2.js for legacy browser JSON support if Backbone.sync is used), which doubles the size of the include. Obviously not a deal-breaker, since both combined are about a third the size of jQuery.

I bet the Heroku guys now know what NASA scientists must feel like; Cloud 2 is their Dasani.

http://www.theonion.com/articles/cokesponsored-rover-finds-e...

Let us resist flashing the patio11 signal for this.

Maybe the Brown students took the survey S/NC:

  Are you happy?[undefined,true]

http://www.brown.edu/Administration/Dean_of_the_College/cour...