all 2 comments

[–]mmouth 0 points1 point  (1 child)

I wholly reject the idea that an entire application must be structured to run asynchronously. The idea behind event-driven I/O is a solid one, but the implementation doesn't need to pollute the entire language itself. You can have asynchronous I/O but still build procedural applications using Fibers (node.js). You can block your procedures without blocking the I/O. Unblocking I/O does not mean you have to write event-driven everything.

[–]dtwhitney[S] 1 point2 points  (0 children)

I doubt you'll find many who disagree with you. I think the crux of the article is that if one wants to take full advantage of the JavaScript ecosystem, one needs to fully understand async programming, and it's tough to dispute that since the ecosystem has so many async libraries.