3 ms·

Node.js v0.8 around the corner

35 points by nodejs-news 14y ago

pooriaazimi 14y ago
The text is copied verbatim without attribution from Node's wiki; I think they should at least link back to it: "API changes between v0.6 and v0.8" : https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8 https://github.com/joyent/node/wiki/API-changes-between-v0.6...
- pooriaazimi 14y ago
  Oh, and I don't know where Joyent announced this news - it certainly wasn't on their blog... and the article doesn't provide any source. The only time I saw anyone mention anything about 0.8's release date, was here: https://groups.google.com/d/msg/nodejs/aRC2pbFN8NU/YXpB_vuCT9YJ https://groups.google.com/d/msg/nodejs/aRC2pbFN8NU/YXpB_vuCT... There are (at least) 7 more open issues before 0.8: https://github.com/joyent/node/issues?milestone=10&state=open https://github.com/joyent/node/issues?milestone=10&state... -- I feel guilty upvoting this story; specially given that submitter is just a dummy account promoting this blog.
  - htilford 14y ago
    izs mentioned @tacoconf that he wanted to get people to switch to 0.8.x @nodeconf
- nodejs-news 14y ago
  Yes I just made a copie paste to let the community know The information come from this 2 @Nodejs tweets : http://twitter.com/nodejs/status/210160851225821184 http://twitter.com/nodejs/status/210160851225821184 and http://twitter.com/nodejs/status/210218802451972097 http://twitter.com/nodejs/status/210218802451972097 Best
bergie 14y ago
Node.js 0.8 sounds great, though I'm afraid there will again be a long period where many of your NPM dependencies are simply broken, especially with the new build tool for native modules: https://github.com/TooTallNate/node-gyp https://github.com/TooTallNate/node-gyp We had a bit of a similar situation with the transition from 0.4 to 0.6 because of some API changes, especially the removal of EventEmitters from the C++ module API: https://groups.google.com/d/topic/nodejs/rmvA434u3Dk/discussion https://groups.google.com/d/topic/nodejs/rmvA434u3Dk/discuss... Hopefully this time it will happen more smoothly.
- catch23 14y ago
  compiling & debugging native libs in node 0.7 is vastly easier, so I'm happy that 0.8 will be here soon. Previously you'd get a pretty generic hardcoded error message about failure to compile/link and it wouldn't be obvious what was the underlying issue. Also, gyp is a lot easier to use than waf -- it just generates the makefiles that are used to do the compilation. The solution was to compile in 0.7 to see the error, then go back to 0.6 to make the module. (I'll also mention I haven't run into any native compatibility issues between 0.6 & 0.7 yet)
- ak217 14y ago
  We had a really craptastic time trying (and failing) to debug what seems to be race conditions in waf (it uses two workers by default, and they get deadlocked intermittently when doing build jobs). So I look forward to at least getting that sorted out by way of node abandoning waf.

35 points by nodejs-news 14y ago

The text is copied verbatim without attribution from Node's wiki; I think they should at least link back to it: "API changes between v0.6 and v0.8" : https://github.com/joyent/node/wiki/API-changes-between-v0.6-and-v0.8 https://github.com/joyent/node/wiki/API-changes-between-v0.6...

pooriaazimi 14y ago
Oh, and I don't know where Joyent announced this news - it certainly wasn't on their blog... and the article doesn't provide any source. The only time I saw anyone mention anything about 0.8's release date, was here: https://groups.google.com/d/msg/nodejs/aRC2pbFN8NU/YXpB_vuCT9YJ https://groups.google.com/d/msg/nodejs/aRC2pbFN8NU/YXpB_vuCT... There are (at least) 7 more open issues before 0.8: https://github.com/joyent/node/issues?milestone=10&state=open https://github.com/joyent/node/issues?milestone=10&state... -- I feel guilty upvoting this story; specially given that submitter is just a dummy account promoting this blog.
- htilford 14y ago
  izs mentioned @tacoconf that he wanted to get people to switch to 0.8.x @nodeconf
nodejs-news 14y ago
Yes I just made a copie paste to let the community know The information come from this 2 @Nodejs tweets : http://twitter.com/nodejs/status/210160851225821184 http://twitter.com/nodejs/status/210160851225821184 and http://twitter.com/nodejs/status/210218802451972097 http://twitter.com/nodejs/status/210218802451972097 Best

bergie 14y ago

Node.js 0.8 sounds great, though I'm afraid there will again be a long period where many of your NPM dependencies are simply broken, especially with the new build tool for native modules: https://github.com/TooTallNate/node-gyp https://github.com/TooTallNate/node-gyp We had a bit of a similar situation with the transition from 0.4 to 0.6 because of some API changes, especially the removal of EventEmitters from the C++ module API: https://groups.google.com/d/topic/nodejs/rmvA434u3Dk/discussion https://groups.google.com/d/topic/nodejs/rmvA434u3Dk/discuss... Hopefully this time it will happen more smoothly.

catch23 14y ago
compiling & debugging native libs in node 0.7 is vastly easier, so I'm happy that 0.8 will be here soon. Previously you'd get a pretty generic hardcoded error message about failure to compile/link and it wouldn't be obvious what was the underlying issue. Also, gyp is a lot easier to use than waf -- it just generates the makefiles that are used to do the compilation. The solution was to compile in 0.7 to see the error, then go back to 0.6 to make the module. (I'll also mention I haven't run into any native compatibility issues between 0.6 & 0.7 yet)
ak217 14y ago
We had a really craptastic time trying (and failing) to debug what seems to be race conditions in waf (it uses two workers by default, and they get deadlocked intermittently when doing build jobs). So I look forward to at least getting that sorted out by way of node abandoning waf.