News for hackers. Stuff that matters.
Re:Plan to throw one away by smegel on Monday December 14, 2015 @10:33PM (#10735726)
> javascript in the server wasn't "too soon", it already existed

Those two things aren't necessarily in conflict. Netscape's server wasn't exactly a roaring success. What really made Javascript-in-the-server work was a Javascript JIT engine (v8) that actually made Javascript very competitive compared to traditional server side scripting languages. So given that there did not exist a Javascript JIT engine back then, maybe it was too soon.

Re:Plan to throw one away by jzwinck on Tuesday December 15, 2015 @01:22AM (#10736278)
SpiderMonkey was around way before v8, and once it begat TraceMonkey, it had JIT. Bloomberg used this pervasively on their billion-dollar product for years before v8 was a thing--you can read that from one horse's mouth here: https://news.ycombinator.com/item?id=3984617
Re:Plan to throw one away by smegel on Tuesday December 15, 2015 @01:49AM (#10736351)
That's quite interesting. I only mentioned v8 for the fairly obvious reason that it formed the core of the first really popular server side JS implementation, which I don't really need to name.
Re:Plan to throw one away by ghayes on Monday December 14, 2015 @11:57PM (#10736025)
Agree that was probably too soon, even if it existed in some form. I've often wondered why precisely people love JavaScript on the server. I would guess it's a mix of 1) event machine parallelism, 2) isomorphism, 3) speed (since V8/SpiderMonkey/Chakra), 4) cross-compatibility, and 5) engineers not needing to learn another language.
Re:Plan to throw one away by eponeponepon on Tuesday December 15, 2015 @06:05AM (#10737093)
I've always assumed it's heavily weighted towards 5 - never underestimate the ability of a coder to avoid effort!
Re:Plan to throw one away by kybernetikos on Wednesday December 16, 2015 @04:00AM (#10743125)
Also, the npm ecosystem.

The early js-on-the-server systems had miserable ecosystems.