Is this equivalent to DHH stepping down?
Clearly not.
If this situation were anything like DHH stepping down there would be a lot more swearing involved.
Ryan Dahl steps down
41–50 of 66 posts
Re: Ryan Dahl steps down
#42Earlier 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. 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…
> 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.
That's great to know. Obviously I'm just following the docs.
> Most of the rest of what you describe is APIs that need to be polished and refined a bit
My concern is merely that there have been a number of statements put out saying "we won't be adding anything more to the API", and that we are basically almost at 1.0, at which point there won't ever be anything added to the core API. Lack of flock() is huge (you can't write to an existing file safely without it - and Node developers are doing that all the time, including your own NPM). Lack of an ability to create temporary files safely seems a fundamental weakness - especially when so many Node apps are dealing with file uploads - that's a disaster waiting to happen. We are going to be dealing with Node.js security bugs because of these issues for a VERY long time.
Re: Ryan Dahl steps down
#43node.js is different. It's not a language, it's a small/extensible set of tools built on top of a solid language, and VM (V8) that are very mature. Node.js is in great hands with Isaac. Unlike many other web/network platforms node doesn't go around gobbling up everything into core. The community behind node is stronger and contributes more than I've seen before. Focusing on that third party module system experience i…
The mark of a great leader is in training new leaders to replace him. That is height of unselfishness.
Re: Ryan Dahl steps down
#44Earlier 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. 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.
The point is that people (core developers) are suggesting it is finished. Follow them on twitter, and subscribe to the mailing list and you'll see.
Re: Ryan Dahl steps down
#45Thanks everyone for the huge vote of confidence. I'm flattered and overwhelmed by the response.
Of course :) You stepping in and writing NPM was HUGE! Along with Ryan, you and guys like Tim, Guillermo, TJ, Felix, now Bert and others really got the ship pointed in the right direction
Re: Ryan Dahl steps down
#46Some rumor... Joyent has taken this decision. Can anyone confirm please?
Re: Ryan Dahl steps down
#47Pure conjecture, but didn't he start complaining/ranting about programming around the time Node.js for Windows was being developed? Maybe it burned him out.
Valid conjecture, but I think Ryan's always had that about him ("Camelcase... how cute")
Re: Ryan Dahl steps down
#48Earlier 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. 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…
THANK YOU. This addresses a question I've had on stack overflow for a couple of days. It also addresses at least two issues in Node.js's github tracker under the 'fs' flag.
Re: Ryan Dahl steps down
#49Sorry 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/
One of the better arguments I can think up against the npm coding style is probably found in the Matador framework, specifically its router: https://github.com/Obvious/matador/blob/master/src/router.js
Note: I actually rather like Matador. I just find this particular style--high density, no semicolons--much harder on my eyes. I'm sure many others can read it better than I can, however.
Re: Ryan Dahl steps down
#50Pure conjecture, but didn't he start complaining/ranting about programming around the time Node.js for Windows was being developed? Maybe it burned him out.
Weren't those complaints about nix's complexity though? The complaints about things like the nix filesystem were specific enough that it's a stretch to point toward Windows.