31–40 of 81 posts
I'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 [1] https://github.com/joyent/node/issues/8718
Awesome! Even better, will Joyent pay me to use it? https://news.ycombinator.com/item?id=8996797 I hope they have enough Timothy J Fontaines.
I'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 [1] https://github.com/joyent/node/issues/8718
So 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.
I'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 [1] https://github.com/joyent/node/issues/8718
Meh, too late. io.js is the standard now.
Not sure if this is a joke, but assuming it's not - it's the standard now, and it's been out for... 2 whole months?!
Barring a merge back into node.js (which could still happen), I don't see myself going back for new projects.
Earlier quoted context omitted.
Example? 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
fibers
I'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 [1] https://github.com/joyent/node/issues/8718
@dap, that's very excited work! Would love to sit with you soon and watch you use the debugger with these enhancements.
Earlier quoted context omitted.
Yep, io.js v1.1 works really fine and i switched too.
My 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.
https://github.com/iojs/io.js/issues/456#issuecomment-730639...
As a native module owner, I made mine work right away and it was work that I needed to do anyway for Node compatibility because changes in v0.11.13/15 broke me as well.