1,040 karma · joined June 30, 2011
https://github.com/andreypopp https://twitter.com/andreypopp
[1]: https://github.com/visionmedia/rework-vars [2]: https://github.com/visionmedia/rework
So did the v8 team do something specially to make asm.js faster? As mraleph said, the answer is no. So the fact that asm.js is now faster in Chrome is side-effect.
It was fixed soon after discovered.
"We added performance comparison with MongoDB. MongoDB is very slow on loading data (slide 59) - 8 minutes vs 76s, seqscan speed is the same - about 1s, index scan is very fast - 1ms vs 17 ms with GIN fast-scan patch. But we managed to create new opclass (slides 61-62) for hstore using hashing of full-paths concatenated with values and got 0.6ms, which is faster than mongodb !"
It's still a rough draft — so expect it to work best only in Blink/WebKit now.
Some shortcuts:
* Arrows — move between blocks
* Shift + Arrows — rearrange blocks
* Enter — creates a new paragraph
* Esc — merge with previous block (only for text based blocks, remove current block otherwise)
* If paragraphs starts with # it transforms into heading (repeat # for more heading levels)
* If paragraphs starts with ``` it transform into code snippet
* Images are entered as 
* HR — *
It's just about 500LOC, Thanks to excellent React[1] library. No inline markup yet, but it's not difficult to add. Also needs some more polishing and tests.
For example in my fork of Dokku I replaced Heroku buildpacks with plain Dockerfiles to define both a stack and a runtime dependencies — https://github.com/andreypopp/upaas
For example I've forked it to built a μPaaS[2] — it has out-of-the-box integration with upstart (for supervision and logging) and replaced Heroku buildpacks with the ability to define stack in Dockerfile (which is much simpler).
[1]: https://github.com/progrium/dokku [2]: https://github.com/andreypopp/upaas
That's the point — using callbacks you end up with functions which do not make sense...
Edit: spelling
Node.js error handling sucks, period.
1) crawl HN for links about X with comments like "How does this compare to Y"
2) present it as a knowledge base of technologies with comparison tables