News for hackers. Stuff that matters.

A comment on Node v4.0.0. Parent comment

Re:Node v4.0.0 by blowski on Tuesday September 08, 2015 @04:46PM (#10188134)
> Isn't that true for many platforms?

I would say that the ROI is lower for time spent learning Node. I've found that with all the other languages I've learnt, in a couple of days I've been able to build something useful, leave it running in production and reuse skills learned a year later.

With Node, even the name of the language is not stable! A few weeks back I went to install Zombie, and now I have to install iojs and not Node. Assumedly it's now Node again. If you live and breathe the language, subscribe to the mailing lists, go to the meetups, etc, these things might be obvious. But when you're just dipping in and out, it really dents your confidence in the language.

[ Parent | on HN ]
Re:Node v4.0.0 by nilliams on Tuesday September 08, 2015 @05:22PM (#10188275)
Your latter paragraph seems a bit fuddy as people 'just dipping in and out' would never have to have contended with the iojs 'name' any more than Python/Ruby/PHP people have to switch to a different VM every time one is announced (e.g. PyPy/Rubinius/Hack).

I'd agree with your first paragraph in that Node is a bit lower-level out of the box and probably takes more effort to get started building a web-app, but I think the time invested jumping in at that low-level is actually useful vs diving in at a higher 'framework level' with some of the other popular web languages.

Also it does have superior installer/package-manager/deployment stories compared to say ... Python & Django, which does have an impact on ROI.

[ Parent | on HN ]
Re:Node v4.0.0 by blowski on Tuesday September 08, 2015 @05:57PM (#10188429)
> Your latter paragraph seems a bit fuddy as people 'just dipping in and out' would never have to have contended with the iojs 'name' any more than Python/Ruby/PHP people have to switch to a different VM every time one is announced (e.g. PyPy/Rubinius/Hack).

One of my main use cases for Node is Zombie, and that required io.js after v3. No mainstream PHP, Ruby or Python application has required a different interpreter.

[ Parent | on HN ]
Re:Node v4.0.0 by mmebane on Tuesday September 08, 2015 @08:39PM (#10189015)
The io.js situation was more akin to Python 3 vs Python 2 than Python vs PyPy. It might not have looked like a major difference at first glance, but there were notable significant, which came with some breaking under-the-hood changes.
[ Parent | on HN ]
Re:Node v4.0.0 by hcon on Tuesday September 08, 2015 @06:10PM (#10188480)
Sounds to me like your issue is with the author of Zombie.
[ Parent | on HN ]
Re:Node v4.0.0 by Touche on Tuesday September 08, 2015 @10:36PM (#10189366)
Actually it's with jsdom, Zombie's major dependency which dropped Node support pretty soon after IOjs was released.
[ Parent | on HN ]
Re:Node v4.0.0 by WalterSear on Wednesday September 09, 2015 @12:57AM (#10189770)
That sounds political, more than anything else.
[ Parent | on HN ]
Re:Node v4.0.0 by thechriswalker on Wednesday September 09, 2015 @10:02AM (#10191476)
Actually, IIRC it's the exact same reason as the io.js split. The maintainer of jsdom had changes that weren't being merged into node's VM module.

So jsdom 3.x used a lib called "contextify". When io.js was released and the changes included, node support was dropped. Now node 4.0.0 is out and has those changes, jsdom now works on node again.

[ Parent | on HN ]
Re:Node v4.0.0 by lfuller on Wednesday September 09, 2015 @03:52PM (#10194027)
It was. The maintainer of jsdom decided to no longer support node after 3.x and made the library throw a condescending exception if you tried to run it with node. The docs were also filled with childish "tm" symbols whenever node was mentioned.

I see things like this all the time and it really puts me off OSS.

[ Parent | on HN ]