4 ms·
Why would MICROS~1 hate be something bizarre? I find such hate quite understandable. I might not share it, but I would not put any trust in MICROS~1 either, es
by cess11 3y ago
Why would MICROS~1 hate be something bizarre?
I find such hate quite understandable. I might not share it, but I would not put any trust in MICROS~1 either, especially not in a professional setting.
When I develop applications for MICROS~1 platforms, I do it in Java, betting that the Eclipse foundation and a plethora of corporations, including MICROS~1, aren't going to suddenly team up and do something nasty to the language and important libraries. With MICROS~1 as the lone manager of a language and most of its 'ecosystem' this seems like a real risk.
- naasking 3y 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 3y agoSure. Organising a community to care for the fork is not.
- naasking 3y 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 3y agoI made no such comparison. No, it's not. Is Mono independent today?