5 ms·
> It promises a stable future, so let's say I'm being cautiously optimistic. This doesn't make sense in light of your initial comment. One of the big goals of
by grandalf 11y ago
> It promises a stable future, so let's say I'm being cautiously optimistic.
This doesn't make sense in light of your initial comment. One of the big goals of IO was to move to semver and address unpredictability/instability that you describe.
If anything, the merging of Node and IO should give you confidence that project governance will be on the right track moving forward.
Also, when you consider the advancements in transpiled js, the js/node community is looking very wise compared with other language maintainers.
- deleted 11y ago[deleted]
- radu_floricica 11y ago"On the right track" does not mean "production ready now". Some time needs to pass in order to create the confidence necessary.
- grandalf 11y agoI lot of people (myself included) have been using IO.js in production for a while now.
- Killswitch 11y agoTell that to the big companies who use it in production right now. Microsoft, Netflix, PayPal, Walmart.
- hexchain 11y ago> One of the big goals of IO was to move to semver And of course they failed right from the start. From semver.org: Version 1.0.0 defines the public API. So their jumping to 4.0.0 from 0.x.x means they don't care to have a public API!
- kbutler 11y agoI'm not sure you're not trolling, but in case you have serious concerns, node.js 4.0.0 incorporates the history of io.js. io.js defined 1.0.0 in early 2015. See https://github.com/nodejs/node/blob/master/CHANGELOG.md https://github.com/nodejs/node/blob/master/CHANGELOG.md and search for 1.0.0