Rick, That's nice. I've been told that Yahoo does have an internal version of Node that you can get via `yinst install ynode`, and they use it a lot. They also pull in changes from the upstream project, and have sent pull requests for bugs that they've fixed. None of that is unusual or outrageous. For a company of Yahoo's size, it makes sense to make sure that all relevant parts of their infrastructure are not black-boxes, and they've done this in the past with many other projects.
However, it IS a dated and wrongheaded approach, in my opinion. Yahoo ought to do what Joyent, Cloud9, Nodejitsu, Microsoft, and others have done, and hire a developer (or several) to work directly on the open source libuv and node projects, in a visible way. Forking, renaming, changing significantly, and then "giving back" is archaic in a day and age when we can all work on the same thing together using modern tools like git and github that make all of this completely visible. If ynode is so great, and ought to be shared, then share it; and if it's not, then why bother with a separate fork? Seems somewhat foolish. But really, none of that is what I was confused about. So, he'd open source ynode. Silly, but ok, whatever. But what's "amateurish" about "Joyent's management of node", exactly? That's a bold claim. A person of Douglas's stature in the JavaScript community ought not to make such bombastic statements in a public presentation unless he's prepared to point to some examples of amateurishness. Imagine if I gave a talk at a conference, where I said that Mozilla's management of the spidermonkey project was amateurish. Then, when Brendan Eich (or whoever is the lead dev on the Spidermonkey project at Mozilla, I don't actually know) emails me directly asking what he's doing that is amateurish, and how I think it could be better, I do not reply to him. I'd expect a lot of people to lose respect for me if I did that, and I'm nowhere near Douglas's level of nerd-fame. On Tue, Sep 18, 2012 at 11:30 AM, rektide <[email protected]> wrote: > > > On Tuesday, September 18, 2012 1:26:13 PM UTC-4, Rick Waldron wrote: >> >> This morning I had a chance to ask Doug, in person, to clarify what he >> meant by his statements about forking Node—as it turns out, his motivations >> aren't sinister, nor are they really outrageous. >> >> Historically, Yahoo forks technologies that it relies heavily on, eg. Unix >> and Apache. This allows them to iterate at their own pace and add features >> they want, when they want them and exclusively to meet their own internal or >> product based needs. As he explained to me, he simply meant that if he was >> asked to be the CEO of Yahoo, he would add Node to the technologies that >> Yahoo maintains its own fork of. Doug also noted that in this hypothetical >> scenario, the "YNode" code would be released as an open-source project >> (unlike forks of other technologies at Yahoo) >> >> >> Seems like way less of a big deal when you actually check sources... >> weird, right? > > > I'm not sure what was clarified. This still seems like an entirely wide open > topic. Aside from "doing it under Yahoo's umbrella," I can't read a single > thing different that Crock would do. > > So, it's still open hunting season all! Game on! > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
