Letting people join the queue without having to stand in line seems like a better solution to me. E.g. make them take a number or use their smartphone tolet them know when their turn is.

I wonder what the ratio would look like if the equivalent was done with a JPEG instead of a PNG.

It's one of the sites on http://www.jimmyr.com

    Funny lion always feasible, innovative policies hatred assured.

Seems like commentary on the fall of ancient reddit.

Looks fun and informative for new programmers. That said I don't understand why this has so many points, and don't really think it belongs here.

Here's a video with more info about these anti-picking mechanisms and how to defeat them:

http://www.youtube.com/watch?v=ZQVsI4qyl3g

I got caught up with this guy's videos and watched all of them because they are so cool. Thanks for the share!

Unfortunately, Java applets are the only way to connect a Midi Keyboard to an HTML5 app.

I imagine Javascript's advantage is because V8 is a JIT compiler. It's unfortunate LuaJIT is not shown since it would probably be around the same level or higher than V8.

I'd also be interested to see Pypy's experimental JIT compared here (or pypy at all, for that matter).

Repeating what I said on Reddit: The Regexp vs. indexOf test seems a little misleading. Generally, .indexOf will be faster, but they seem to have performed a very specific test that requires the indexOf method to do some string concatenation before actually searching, which IMO invalidates the usefulness of the test.

Please correct me if I'm wrong.

The test I'm talking about: http://jsperf.com/regexp-indexof-perf

The point of this test is to show that you should avoid making blanket assumptions about performance and that you shouldn't fear the RegExp :)

You can see my full reply here: http://jsperf.com/regexp-indexof-perf#comment-3

You're still testing concat + indexOf, not just indexOf. I think that test is broken.

The test isn't broken in the scope of its use case. You are totally missing the point which is RegExp's are no longer a guaranteed fail when it comes to performance and that in many situations, including that jsPerf test, can out perform the indexOf equivalent.

I think that a lot of people would just like to see a direct comparison, that's all.

Made an updated version of that script here: http://userscripts.org/scripts/show/125021