4 ms·
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
by calroc 13y ago
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."
- mcantelon 13y agoAgreed that no language/framework should be the default. Best tool for the job and all that.
- ricardobeat 13y agoYou 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-questions-with-creator-ryan-dahl/ http://bostinno.streetwise.co/2011/01/31/node-js-interview-4... [2] http://www.youtube.com/watch?v=jo_B4LTHi3I http://www.youtube.com/watch?v=jo_B4LTHi3I
- calroc 13y agoCheers, I will do.
- empthought 13y ago> single-threaded, evented Those are drawbacks. Fatal ones, in fact. They are distinguishing characteristics of microcomputer OSes of the 80s.
- ricardobeat 13y agoAre you talking about cooperative multitasking (vs preemptive)? Though modern OSs went a different route, it clearly works very well for servers and node.