Hacker News Reader

All points for working code, and let me confess ignorance up front right now.

Really my irk comes down to something along the lines of, "Well why not write it in Go or something? Why JS?" and thinking that the only really good answer to that is "Well, we really like JS."

View on HN

You should read this interview [1] and watch the talk [2] by node's creator Ryan Dahl to get a better understanding of where it comes from. There was much more to it than "we really like javascript" (tldr: single-threaded, evented, dynamic, freedom to write new I/O apis, backed by huge companies, well known).

[1] http://bostinno.streetwise.co/2011/01/31/node-js-interview-4...

[2] http://www.youtube.com/watch?v=jo_B4LTHi3I

Cheers, I will do.

> single-threaded, evented

Those are drawbacks. Fatal ones, in fact. They are distinguishing characteristics of microcomputer OSes of the 80s.

Are you talking about cooperative multitasking (vs preemptive)? Though modern OSs went a different route, it clearly works very well for servers and node.

Agreed that no language/framework should be the default. Best tool for the job and all that.

Reply on news.ycombinator.com