2 ms·
I don't hate it I just won't use it because I don't like its characteristics at the moment: * Javascript : don't like it. This "[3,1,10,2,].sort()= [ 1, 10, 2,
by rdtsc 14y ago
I don't hate it I just won't use it because I don't like its characteristics at the moment:
* Javascript : don't like it. This "[3,1,10,2,].sort()=
[ 1, 10, 2, 3 ]" is broken. Don't care about the historical explanations or philosophical arguments about strong or weak typing. It's broken and that's that.
* Nested callbacks. I don't like that. I like green threads and/or processes for handling concurrency. I'll take Go, Scala, Rust, or Erlang's (processes|channels|actors) instead, if not I'll take any green threads.
* Single threaded : server sits there with 16 cores, it's nicer to use something that can automatically scale across them. This also means if any deeply nested callback functions ends up blocking the whole node process stops.
Not trying to upset anyone at Joyent or others who put effort into, just my personal preferences. It is not that Node is bad, it's pretty good, it is just that I don't see a reason to use when they are much better tools out there.