I've been searching high and low for info on this subject, so please forgive me (and redirect me) if this topic has been discussed elsewhere.
I understand why Cycling is walking away from development of the Max/MSP runtime to focus on M4L (as Live itself is now the runtime for all practical purposes), but I'm curious if any outside groups have discussed taking up the challenge of continuing to develop the current runtime (or a fresh runtime) independently (ala an open/free project presumably). I understand that, to the best of my knowledge, Cycling has not publicly discussed any plans to release the source code for the current runtime. . .
Are developers who are using Max/MSP to create commercial or community-supporting plugins/apps just planning to update their plugs for M4L, and face a future where only M4L owners (and maybe, at some point, all Live owners) can use their products?. . . (lest they face the harsher reality of having to recreate their products in C++/Juce and handle continued OS/DAW update fixes and compato themselves).
If I'm mistaken about any aspect of Cycling's future plans or what the usefulness of a continually-updated non-Ableton, non-M4L runtime would be, please correct me.
Thanks to anybody that can point me in the right direction.