4 ms·
You have seen what the author posted later on in the discussion? https://github.com/sam-mccall/node-plate https://github.com/sam-mccall/node-plate
by abp 16y ago
You have seen what the author posted later on in the discussion?
https://github.com/sam-mccall/node-plate https://github.com/sam-mccall/node-plate
- DanielRibeiro 16y agoThere are soo many interesting ways to solve this: http://news.ycombinator.com/item?id=2101724 http://news.ycombinator.com/item?id=2101724
- Sidnicious 16y agoIs that the wrong link, or are you threadjacking?
- DanielRibeiro 16y agoWow, wished I saw it earlier (can't edit now). Bad paste. Correct link: http://www.infoq.com/articles/surviving-asynchronous-programming-in-javascript http://www.infoq.com/articles/surviving-asynchronous-program...
- gregschlom 16y agoLink unrelated
- liuliu 16y agoI like this syntax more: https://github.com/creationix/do https://github.com/creationix/do
- moe 16y agoI like neither. They're still riddled with boilerplate (anonymous functions) and are quite horrible to read and write (bracket nesting). I sometimes wish node.js (and js in general) would adopt co-routines. They'd seem to be the perfect middle-ground here; async code that looks almost like threaded-code, and no more callback-hell.
- sam-mccall 16y agoAnd later still: https://github.com/sam-mccall/node-ship https://github.com/sam-mccall/node-ship (supports a few more things than just method chaining)