News for hackers. Stuff that matters.

A comment on What the web platform can learn from Node.js: The Darwinism of small modules. Parent comment

Re:What the web platform can learn from Node.js: The Darwini... by sotojuan on Wednesday December 16, 2015 @02:06PM (#10746432)
It doesn't have to be this way. At least stuff like Elm forces semver on your projects. It detects if your new version has breaking changes and won't publish it unless you bump it up a version. That said, Elm is super niche and will probably never be popular. But my point is, there's people doing it right.

I too am confused about Babel 6... but to be fair I haven't looked too much into it. I just think it's weird that something as "simple" as doing ES2015 -> ES5 now has plugins and a whole ecosystem around it. I understand the creator's ambitions, but I'd prefer to just install it and plug it to my build system.

I don't know much about Go, but I am personally looking into Elixir as another backend choice.

[ Parent | on HN ]
Re:What the web platform can learn from Node.js: The Darwini... by tracker1 on Thursday December 17, 2015 @02:20AM (#10750095)
It's not just ES6/7 transpilation though... there are a lot of ES6 features that are in node, and modern browsers, so not everything needs to be translated all the time... let alone more advanced options like flow and jsx (more than just for react, but mercury and others).

That's why the change, I do think they pulled the gun a bit soon though, but many would have jumped to it just the same.

[ Parent | on HN ]