“Node.js is one of the worst things to happen to the software industry” (2012)

Re:“Node.js is one of the worst things to happen to the soft... by mhink on Tuesday August 23, 2016 @03:02PM (#12346492)

> This was addressed through Promises and more recently Observables, Generators, and async/await.

Parent is talking about ES2015 constructs (or ES2016, in the case of async/await). I don't think anyone will disagree that doing async stuff in ES5 is a massive PITA- but it's a bit disingenuous to claim that the newer Javascript specifications aren't doing enough to fix those problems.

That said, four years ago I would have agreed with you- Coffeescript seemed to be the only game in town making an effort to improve the state of Javascript. But I think the embrace of transpilers in front-end engineering has only helped Javascript thrive, by allowing the community (and core developers) to more easily determine what features will actually make the language better.

(On a completely unrelated note, nice username- DCSS reference?)

[ Parent | on HN ]

Re:“Node.js is one of the worst things to happen to the soft... by OOPMan on Wednesday August 24, 2016 @02:28AM (#12350126)

I've started using async/await and it is something of a game-changer in terms of code readability.

Promises were nice but also subject to nesting and readability problems which the new addition solves nicely.

[ Parent | on HN ]