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…
Ryan Dahl steps down
11–20 of 66 posts
Re: Ryan Dahl steps down
#12Re: Ryan Dahl steps down
#13Does anyone have a link that doesn't require me to login to see this?
Re: Ryan Dahl steps down
#14What 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
#15EDIT: edited a bit in the form to make my thought more clear.
Re: Ryan Dahl steps down
#16Re: Ryan Dahl steps down
#17node.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…
Re: Ryan Dahl steps down
#18Best of luck to him, he's sure gonna need it!
Re: Ryan Dahl steps down
#19Is this equivalent to DHH stepping down?
Re: Ryan Dahl steps down
#20positive: 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.