Re:Adding a new Bytecode instruction to the .NET runtime
by benaadams on Saturday May 20, 2017 @01:07PM
(#14383289)
> C# moves fast because it mostly only Microsoft calling the shot, even if they are now taking input via Github.
Is Microsoft, RedHat, JetBrains, Unity, Samsung and Google (Also Mono and Xamarin - though they are now part of Microsoft) - as well as the wider community via GitHub etc
Re:Adding a new Bytecode instruction to the .NET runtime
by pjmlp on Saturday May 20, 2017 @01:40PM
(#14383446)
.NET Foundation was created when .NET went open source, about two years ago.
Still very new and so far Microsoft has been driving most of it, as one can see from the Github architecture meetings.
It is bit different from JCP which goes all the way back to 1998.
Just having the logos on the .NET Foundation web site doesn't mean those companies are driving language decisions.
C design is driven by committee with deep respect for backwards compatibility, despite the inherent security flaws, the language differences between C11 and C89 are superficial.
Likewise, in spite of having Oracle at the helm, Java's design is driven by the JEP working group.
When the majority of the world depends on Java, cannot add language features just because they look cool.
C# moves fast because it mostly only Microsoft calling the shot, even if they are now taking input via Github.
We just saw Java politics recently with IBM and Red-Hat vetting jigsaw because it isn't a copy of OSGi.