Live data from Hacker News

Ryan Dahl steps down

groups.google.com

11–20 of 66 posts

Re: Ryan Dahl steps down

#11
post #6

What 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…

node.js isn't a language.

Re: Ryan Dahl steps down

#13

Does anyone have a link that doesn't require me to login to see this?

"Now that the rewrite on top of libuv is largely complete, I am ceding my position as gatekeeper to Isaac Schlueter. Our energy will now be largely focused over the next few months on improving the third party module system experience including a website for browsing modules, a new addon build system, and binary installations from npm. Isaac is in the unique position to bridge the gap between core and external modules to ensure a pleasant experience. After three years of working on Node, this frees me up to work on research projects. I am still an employee at Joyent and will advise from the sidelines but I won't be involved in the day-to-day bug fixes. Isaac has final say over what makes it into the releases. Appeals for new features, changes, and bug fixes should now be directed at him. "

Re: Ryan Dahl steps down

#14
post #6

What 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…

node.js isn't a language.

Linux isn't a language either, but they have Linus since forever.

Re: Ryan Dahl steps down

#15
It makes a lot of sense to move forward at some point, but this time the timing is a bit suspicious: now that node.js started to have a lot of traction the lead developer stepping down is a bit unexpected. My guess is that there is some very exciting new adventure in the Ryan's future, or that sometimes three years are simply enough from a "feelings" point of view. Anyway best fishes for the future.

EDIT: edited a bit in the form to make my thought more clear.

Re: Ryan Dahl steps down

#17

node.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…

This change is a sign of Node's shift from improving the core to making modules work better. I see it that way, at least. Isaac is the author of npm after all.

Re: Ryan Dahl steps down

#20
negative: 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 module developers. They're good but like most documentation done by the original developers make too many assumptions about what readers know. I don't mean to be too critical but if users are going to Stackoverflow for answers then there is a problem.

Post reply on HN