I always learn something when I write my posts, but it nice to know I'm not the only one
And now that it's open-source it's easy to look under the hood and have a play around
Even though it's written about the Shared Source code (.Net 2.0), lots of the info in the book still applies
Or is there a strict limit to the number of instructions, with existing "unused" entries for all of the free ones?
What about using Windbg with the sos.dll extensions?
I wonder if the author considered writing a book, kind of modern Shared Source CLI Essentials (that I read years ago and hold in high regard)?
Now there's an idea :-)
BTW I've been bugging/asking the author of the SSCLI book if he has any plans to update it, see http://mattwarren.org/2017/05/19/Adding-a-new-Bytecode-Instr...
Using cmov you can improve performance a bit.
Something is seriously wrong with some companies.
Edit: To those downvoting, remember, if you disagree, post a reply.
As for Java, they were already selling Java based products around 2000 and former Sun employees like James Gosling, were not happy with Google actions but Sun had run out of money for any kind of lawsuits.
Also it is easy to write angry posts about Oracle's decisions, but if Google, Red-Hat or IBM actually cared that much about Java's future they would have given work to those driving the future of the language, instead of ignoring them.
I look at all of the innovations and convenience features that C#(an unashamed Java clone at the start) has introduced in the meantime, and it makes me wonder what is so broken with Java.
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.
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
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.