> I'm not going to add support for a fork lightly; I don't think this will stick; and I don't think a fork is an appropriate or well-timed response to what's been happening. Either way, I wouldn't add support for a fork that adds nothing but a partial documentation commit - that has value for nobody.<p>I appreciate this straightforward and honest response to this issue. The responder has looked at the benefits of the fork and decided that it doesn't make sense to add it.
Looking at the forked repo all they did was rename node to ayo and add a VALUES.md with very little substance. Looks like a power grab by a bunch of control freaks to me.<p>At least io.js had some technical merit and seemed to genuinely want to improve node (which arguably it did).
I haven't gone very deep with this issue, but I worked with Rod briefly at Nodesource, and hope more node-ecosystem projects respond like this. In the short time we worked together, I was completely impressed with him technically and socially. I was really surprised when I heard that anyone had an issue with him. I specifically remember the COC (which I guess this is about) was mandatory for all projects, and it's adherence was extremely important. I think he has very high standards of quality, but never personally saw any kind of hostile behavior (I'd say the opposite, as he was always really helpful.) He is an asset to any team, and I hope this blows over soon, so he can get back to doing what he's good at.
On the subject of version managers for multiple programming languages, people might be interested in checking out asdf [0]. nvm was my favorite tool for handling multiple node versions, but I've found asdf suits my needs a bit better.<p>I'd still reach for nvm for deploying to a server. To the best of my knowledge, the code is portable across all UNIX-y OSs.<p>On the other hand, asdf supports multiple languages, so I was able to kill off rvm too! It also has considerably better performance (specifically, startup speed).<p>EDIT: As to the discussion regarding Ayo.js... I've never interacted with Rod personally, but having read a few hundred of his miscellaneous responses on GitHub, he has never struck me as someone unreasonable. His response to the criticisms being raised seem very reasonable as well. If anything, I now feel like I have a bit more trust on node team.<p>Based on my highly limited outsider's perspective, trying to kick him seems overly harsh. If people believe he's doing things poorly, an avenue should be created through which constructive criticism and feedback can be provided. We're all human, we make mistakes, and we sometimes don't understand each facet of problems we encounter.<p>[0] <a href="https://github.com/asdf-vm/asdf" rel="nofollow">https://github.com/asdf-vm/asdf</a>
Jordan has apparently walked that back.<p><a href="https://github.com/creationix/nvm/issues/1595#issuecomment-325159240" rel="nofollow">https://github.com/creationix/nvm/issues/1595#issuecomment-3...</a>
Maybe now we've got goddam, real, actual Nazis to worry about people can stop expending effort in creating straw nazis out of thin air.<p>Bigger fish to fry, people...