down from what?
Ryan Dahl steps down
31–40 of 66 posts
Re: Ryan Dahl steps down
#32Does anyone have a link that doesn't require me to login to see this?
Does anyone have a link that doesn't require me to login to see this? This is a google groups quirk. If you are logged into a google account it will prompt you. If you sign out of your google accounts then you can read it without being logged in.
I am not logged into my google account.
Re: Ryan Dahl steps down
#33negative: It would have been nice to see a 1.0 release before this happened. positive: Without the originator in place perhaps a more formal product infrastructure can be put in place by Joyent. I'm thinking in particular about a structure for the documentation of primary third party modules like Connect and Express. At present the readme's and examples on Git, Sencha, and ExpressJs are all done by the original modul…
At present the readme's and examples on Git, Sencha, and ExpressJs are all done by the original module developers
I don't get this. Why would a core team be responsible for the documentation of 3rd party modules.
Node has some serious documentation issues but I'm not sure how Ryan or Joyent is responsible for anything outside of anything under nodejs.org/docs
Re: Ryan Dahl steps down
#34Earlier quoted context omitted.
Honest question: have you actually tried working with modules and dependencies in Node? It's better now, but it's still not pleasant and often installing a module starts with debugging. And what's the core missing, would you say? Personally, I thought the cluster stuff was already getting heavy.
> Honest question: have you actually tried working with modules and dependencies in Node? It's better now, but it's still not pleasant and often installing a module starts with debugging. Yes. And you're right, but then it's not often that much better than other languages. Personally I'd rather they get the core language finished first (though their concept of "finished" and mine seem to differ). > And what's the cor…
You can open a file with O_EXCL if you pass in the open flags as a number. (You can find them on require("constants"), and they need to be binary-OR'ed together.) This isn't documented. It should be. It should probably also be exposed in a cleaner way.
Most of the rest of what you describe is APIs that need to be polished and refined a bit. The boundaries are well defined at this point, though. We probably won't add another builtin module at this point, or dramatically expand what any of them can do. (I don't consider seek() dramatic, it's just tricky to get right given JavaScript's annoying Number problems.)
Re: Ryan Dahl steps down
#35Thanks everyone for the huge vote of confidence. I'm flattered and overwhelmed by the response.
Re: Ryan Dahl steps down
#36Earlier quoted context omitted.
Honest question: have you actually tried working with modules and dependencies in Node? It's better now, but it's still not pleasant and often installing a module starts with debugging. And what's the core missing, would you say? Personally, I thought the cluster stuff was already getting heavy.
> Honest question: have you actually tried working with modules and dependencies in Node? It's better now, but it's still not pleasant and often installing a module starts with debugging. Yes. And you're right, but then it's not often that much better than other languages. Personally I'd rather they get the core language finished first (though their concept of "finished" and mine seem to differ). > And what's the cor…
I don't know that anyone is suggesting that it's "finished". In fact, it's not even to a 1.x release yet. I consider anything below that a work-in-progress at at minimum. Generally anything under a 2.x release has lots of room for improvement.
The fact that they're shifting focus isn't a big concern. I'd at least wait until Isaac comes out and says what the future roadmap is before criticizing it.
Re: Ryan Dahl steps down
#37I sort of had a feeling this was coming for a while. Isaac has been doing more and more of the release updates on the blog, not to mention the increasing shift in commits on GitHub from Ryan to Isaac.
Re: Ryan Dahl steps down
#38Wow, what was the last language whose creator stepped down so quickly? Either way, Isaac has been a huge source of energy since the beginning, so im glad its going to him. Congrats all around
Inane trivia alert.. Ryan was at the helm of Node.js 2009-2012. The original JRuby creator, Jan Arne Petersen, was at the helm 2001-2004.
Re: Ryan Dahl steps down
#39What does this mean for the Node community at large? I recently had the pleasure of checking out the NodeUp podcasts. A large portion of the first episode is dedicated to enforcing the notion that Node is a new language, and that it will take decades to catch up to the maturity that Python and Perl provide as platforms. Opening up a subprocess, or having an `os` module which works in Windows, for example, all seemed…
> Opening up a subprocess
I'd take require('child_process') over python's subprocess any day.
Re: Ryan Dahl steps down
#40Sorry to be negative, but I hope this doesn't mean that we're going to start seeing more of node's code in the npm style.
I hope not.
Edit: I don't know of too many prominent JavaScript programmers who prefer not to use semicolons. http://dailyjs.com/2012/01/12/style/