Ran across this article this morning. Read it with your morning coffee. http://readwrite.com/2014/08/22/nodejs-node-js-tj-fontaine-version-10
API stability is certainly important. That said, there's already so much dependency on Node 0.X that any substantial changes will already no doubt have an impact. I love that they're trying to stay away from version fragmentation like Python and Ruby both seem to be afflicted but if a significant change in API is unavoidable then there's not much that can be done.
I'm pleased with how quickly the Advisory Board is coming together. It seems like it was just announced a few days ago. Good to see the charter is up on the NodeJS website now too.
I love the idea and I think it's got potential to keep Node on track. An interesting snippet from the charter is the makeup of the board:
- The Node.js Advisory Board will have 13 members
- The Node.js core committers project lead: TJ Fontaine
- 2 seats for the top core technical contributors
- Up to 8 additional seats: 4 corporate seats, 4 “user” seats
- One curator seat
- One Open Source Software guidance seat
- No fee or sponsorship is required for membership
- The membership term will last 12 months. With the exception of the Project Lead, all members can serve a maximum of two consecutive terms
Oddly, I'm pretty okay with the corporate presence, I would suspect those seats will no doubt go to the early adopters of NodeJS like Walmart, PayPal, and the likes. I'd say they deserve an influence on the project and most certainly have its best interests in mind.
Versions are nothing but a point in time of feature sets and the health of a product.
Does it need to go 1.0, I think this is more concern for non technical leaders to make decisions. It's easy to say let's use PHP over Node because PHP is cheap to hire, and PHP is in a stable version of 5.5 or whatever the case is right now.
The fact that big names early adopted Node (and succeeded with it) will only propel the future of Node forward. Also another factor to help in Node's favor, is making it more cost effective to host and easier to deploy in addition hosting services offering FREE for beta and prototype builds. So that a new developer do not have to worry about this hurdle.
I know I talk a lot about Meteor, but for example when I first got into Node I tried to launch a "Hello World" application to the world, and I had to get AWS, node forever package, had to then port forward port 3000 to 80 or something like (which was like ?! at the time) etc, to just deploy my application to a server. Heroku at the time wasn't offering Node hosting if I remember correctly.
With Meteor I just had to type in my terminal "meteor deploy mak.meteor.com" and it deployed my "Hello World" application quickly without having to worry about much, this helps keeping developers focused on building MVPs.
I love what Meteor has done. It just goes to show what a 12 million dollar investment in an open source project can do.
I'm always excited to build out server environments but there's no doubt that this is a time killer when all you're trying to do is build a Hello World.
I'm really happy to see Meteor taking off. Their new sexy website, all of the publicity, the future is really looking good for the framework.
Node.js has been officially forked to io.js
Holy smokes, now this is interesting.
But for Joyent CTO Bryan Cantrill, Node is alive and well, despite the slower pace of development. He says that Joyent has been focused on making Node faster and more stable, rather than adding new features. “You’ve got to look at the quality of contributions,” he explains, “not the quantity.”
I wonder if the above is something they really believe in, or if it's a PR thing. If what Bryan Cantrill is what they're going to do at the core of Node.js this could be a major win for Node.js.
Node finally gets a .12 release http://blog.nodejs.org/ and Joyent announces it will release control to a new governing body http://readwrite.com/2015/02/10/joyent-node-js-foundation. Could Io.js have been successful in getting things moving?
I'm feeling a bit more confident in things for now.
yup it looks like Joyent got the memo. I read in another article (didn't save the link :) that Joyent would like io.js to merge back into the Node code base but talks are still ongoing.
I just wanted to plug this article on using nvm to manage nodejs and iojs by @EranSch