3 ms·
> With MICROS~1 as the lone manager of a language and most of its 'ecosystem' this seems like a real risk. Why? All of the code is MIT licensed. If MS does any
by naasking 2y ago
> With MICROS~1 as the lone manager of a language and most of its 'ecosystem' this seems like a real risk.
Why? All of the code is MIT licensed. If MS does anything untoward, forking it is trivial.
- cess11 2y agoSure. Organising a community to care for the fork is not.
- naasking 2y agoXimian and Mono were built almost immediately after .NET was released and provided a decent multiplatform community-supported alternative for years, but you somehow think that forking an existing and working codebase would be more difficult than a completely independent reimplementation? Look, there are obvious differences in how Java and the JVM are maintained and evolved as compared to .NET, but to continue claiming that these differences really matter all that much is just FUD, to put it politely.
- cess11 2y agoI made no such comparison. No, it's not. Is Mono independent today?