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.
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...