4 ms·
They could call it MSJVM 2, but that would risk reminding people of what happened the first time Microsoft got involved with Java. That time, according to inter
by ptx 3y ago
They could call it MSJVM 2, but that would risk reminding people of what happened the first time Microsoft got involved with Java. That time, according to internal memos revealed in the antitrust trial, their objective was to kill Java via sabotage of cross-platform Java applications by "polluting them with Windows specific stuff" [1].
Replacing cross-platform build tools with MSBuild might be a good approach if they want to have another go at it. They could build some really convenient integrations with VS Code and Azure. Maybe even integration with WSL2, so that your Java app for Linux only builds on Windows.
[1] https://www.justice.gov/atr/memorandum-united-states-support-motion-preliminary-injunction-us-v-microsoft-corporation https://www.justice.gov/atr/memorandum-united-states-support...
- karianna 3y agoYeah, we're not going to do that :-). The Microsoft Build of OpenJDK is very much a build of OpenJDK that Azure customers can get free support for and over time get some Azure specific performance benefits from. Those performance benefits will be worked on upstream as well (like this escape analysis patch was) but there will be times where upstream won't want to take a patch on a stable LTS branch for example. We'll continue to be very clear when we have a patch that is not in the upstream code and it'll always be available on our GitHub under the GPLv2+CE license.