9 ms·
Node v0.12.0 (Stable)
- wereHamster 12y agoNo mention which version of V8 they use. Did they sync with what Chrome is using nowadays? Anyways, I've already switched to iojs. I'm sharing part of my code between server and client and it has become increasingly painful to work around the lack of progress on the nodejs side of the network.
- domenicd 12y agoNope. They're using V8 3.28.73 and libuv 1.0.2, both of which are abandoned by their maintainers.
- deleted 12y ago[deleted]
- maxogden 12y agoiojs 1.1.0 V8 version 4.1.0.14 (current). nodejs 0.12 V8 version: 3.28.73 (>6 months old). More info here: https://iojs.org/es6.html https://iojs.org/es6.html
- Kiro 12y ago> I'm sharing part of my code between server and client How? And why is it a problem with node but not iojss?
- maratd 12y agoYou can easily use the same framework both on the server and client, especially a general purpose one. Makes life easier. io.js uses the current version of V8. node uses an outdated one. Makes life easier if your code is being executed in the same engine, with the same version. Everything that works in one, works on the other.
- deleted 12y ago[deleted]
- wereHamster 12y agoBecause Chrome and Firefox now provide many ES6 features which are missing from nodejs. But iojs tracks the latest stable v8 so it is feature-wise at the same level as Chrome.
- muaddirac 12y agoAs a casual node user, I'd love to better understand how this release compares to io.js. Are they diverging more? Is node playing catch-up?
- nailer 12y agoNode inspector should now work properly like it does on iojs (https://github.com/joyent/node/issues/7102 https://github.com/joyent/node/issues/7102) but this still isn't a stable v8, according to the v8 maintainers.
- deleted 12y ago[deleted]
- pfooti 12y agoio.js is built against a much more current version of V8, which notably has default-on support for a lot of ES6 stuff. Quite frankly, as a casual node user myself, I'm sticking with node v0.10 for the time being. I want to see how everything shakes out, and my site runs okay for now.
- Jare 12y agoI think the next security "situation" in node and/or io will be a key decision point for many of us in similar situations.
- antouank 12y agoMeh, too late. io.js is the standard now.
- prottmann 12y agoYep, io.js v1.1 works really fine and i switched too.
- Touche 12y agoMy experience has been that just about every module that uses native code (there are more than you think) doesn't work in IO.js because of the changes to the V8 apis. So until all of those are updated to work with both I'll have to stick to Node.
- AnkhMorporkian 12y agoI've had the opposite experience. I've only had a couple modules that use native code that haven't worked, and most of those monkeyed directly with V8 so I wasn't terribly surprised they didn't work with the upgraded version.
- jekrb 12y agoExample? I'm curious because mostly everything has worked for me. I'm using: io.js v1.1.0 npm v2.4.1 node-gyp v1.0.2
- throwaway5611 12y agoAwesome! Even better, will Joyent pay me to use it? https://news.ycombinator.com/item?id=8996797 https://news.ycombinator.com/item?id=8996797 I hope they have enough Timothy J Fontaines.
- geofft 12y ago"Pay" seems like a stretch. The only "money" is in Joyent hosting credit, no?
- felixrieseberg 12y agoGood to see that a new version is out - if anybody here wants to take it for a spin on Azure Websites, we at Microsoft just created a small one-click script[1] that installs this version. [1]: https://github.com/felixrieseberg/node12-azure https://github.com/felixrieseberg/node12-azure
- sync 12y agoSo can I use generators without a --harmony-generators flag now? Surprised there aren't any mentions of ES6 in the blog, considering the competition from io.js.
- neumino 12y agoThey didn't catch up on v8 and libuv and they didn't deliver the supported C++ API. Congrats on the release, but it's kind of disappointing.
- deleted 12y ago[deleted]
- bcantrill 12y agoSeveral have asked about node.js in contrast to io.js. It's fair to say that the emphasis of node.js at this point is on stability (including API stability, production debuggability/observability, etc.) and performance -- in that order. It definitely takes longer to release software when operating under these constraints; as the team writes in the linked blog entry: We are also pleased to report that this release of Node.js has tests passing on all of our supported platforms. On the one hand, this seems obvious (what are tests for if not to verify before you release it?!), but this is actually the first release of Node.js that has operated under this constraint. Requiring that all tests pass before releasing Node.js marks an important development for the project, and is essential for building a solid path moving forward. It's unclear what the divergence will be in the future, but the emphasis of the node.js team on stability may or may not be shared by io.js -- and in particular, this may be reflected in things like the V8 version, changes in which tend to subtly break esoteric things on different platforms. Inasmuch as the divergence represents different operating principles (i.e., enterprise-grade stability vs. bleeding edge), it may well be helpful -- and I think it's entirely conceivable that the projects will develop a symbiotic relationship moving forward.
- wereHamster 12y agoWhy don't you push nodejs forward and track the latest v8 (or whatever the latest stable chrome is using), and then cut LTS releases at regular intervals, kindof like the kernel or ubuntu? Also, are these tests public? How many does iojs pass/fail?
- tellnes 12y agoThat is the plan for io.js. Doing releases often and LTS at some interval.
- nailer 12y agoHow does the stability concern gel with a unmaintained v8?
- bcantrill 12y ago
- ocfx 12y agoyeaaaahh, speak to me when you have a RC
- dap 12y agoI'm really excited that this version of Node includes updates I made for the debugger module[0], including the ability to show you the closures in your program[1]. (This has already helped nail some memory issues in Node itself.) I hope to blog about it in more detail next week. [0] https://www.joyent.com/developers/node/debug/mdb https://www.joyent.com/developers/node/debug/mdb [1] https://github.com/joyent/node/issues/8718 https://github.com/joyent/node/issues/8718
- spicyj 12y agoThis sounds really interesting. I'm excited to see your blog post.
- ryanstevens 12y ago@dap, that's very excited work! Would love to sit with you soon and watch you use the debugger with these enhancements.
- dap 12y agoCool idea. I'll be demo'ing them at NodeSummit too!
- yunong 12y agoThis is fantastic. I know we'll be using the closures feature ourselves to debug our production problems. This is what I love to see in robust software releases -- features that help engineers more easily debug problems. Kudos dap!
- deleted 12y ago[deleted]
- dap 12y agoIf anyone's still following this thread, the blog post is up: https://www.joyent.com/blog/debugging-enhancements-in-node-0-12 https://www.joyent.com/blog/debugging-enhancements-in-node-0...
- jtwebman 12y agoI am glad this is out but bummed about the V8 engine being so old. I see why IO.JS is a thing now but I also understand you want stability as well.
- onestone 12y agoI disagree with the assumption that old === stable.
- kolev 12y agoCompetition at its best! Days after io.js gets released, node.js outs a major release.
- azurelogic 12y agoBoth this and io.js 1.1.0 are available via nvm now.
- btbuildem 12y agoI would just like to point out people are running production stuff on v0.x of something..
- jkrems 12y agoYes, but what's your point? That version numbers aren't the best indicator for production readiness?
- coldtea 12y ago"People" including major companies with huge teams of dev-ops. It's not like 0.x universally means "not production ready" and you know better to school them. The version number only has a meaning within the culture of a specific project. For node, they decided to keep using the 0.x release number long after the product was mature for production use.
- shna 12y agoIt's been 5 years since node.js is around? is node.js development slow or the version numbers (scheme) is progressing slow. It sounds like there is at least a decade for ver 1.0. Probably 1.0 does not mean anything. In my mind version 1.0 is the when the product is complete.
- fnordsensei 12y agoDon't stare yourself blind at version numbers, they're just a way to distinguish one version from another. Open source projects generally don't follow the same versioning conventions as closed source projects, as they don't require you to fork over money for each sharp version. Also, software can rarely ever be said to be "complete", even theoretically. Only very small programs can be written once and be said to fulfil their purpose from then on. For larger programs and systems, the needs and requirements is usually something you try to approximate with ever increasing precision. But usually needs and requirements is a moving target as well, making this task perpetual. This conspires to make 1.0 more of a marketing decision than to map to any real "completeness". I've seen whole program rewrites in a 0.01 change of an open source project. Similarly I've seen projects bumped to 1.0 with very little ceremony simply because it's been used in production for 8 years now, and why the hell not?
- fapjacks 12y agoI actually looked but couldn't find it in my links, but out there on the internet somewhere is an interesting marketing study showing how profoundly more likely people are to pay for software that is versioned at least 1.0. All of my personal projects are 0.x.x, rarely making it to 1.0. Meanwhile, my business projects rarely start under 1.0.