Reading through the posts, this one struck me as the best solution...
"Personally, what I would love to see is io.js take the Node name and handle all of the development through the community. Joyent could then select specific releases that they will support as LTS for enterprises, complete with the requisite paid support packages. That seems like it might be a scenario where everyone could win."
Not only is it a practical solution that fixes problems on both sides, there are examples of similar arrangements that have worked out well, such as the symbiotic relationship between RHEL and Fedora.
That's what happened with GCC and EGCS. Tired from GCC's slow development, some developers created the EGCS fork. After a couple years, the EGCS fork became the official FSF GCC. A detailed history is here:
Comments
Reading through the posts, this one struck me as the best solution...
"Personally, what I would love to see is io.js take the Node name and handle all of the development through the community. Joyent could then select specific releases that they will support as LTS for enterprises, complete with the requisite paid support packages. That seems like it might be a scenario where everyone could win."
Not only is it a practical solution that fixes problems on both sides, there are examples of similar arrangements that have worked out well, such as the symbiotic relationship between RHEL and Fedora.
That's what happened with GCC and EGCS. Tired from GCC's slow development, some developers created the EGCS fork. After a couple years, the EGCS fork became the official FSF GCC. A detailed history is here:
http://www.softpanorama.org/People/Stallman/history_of_gcc_d...
Interesting, didn't know that, thanks cpeterso.