JDeli vs. Microsoft Build of OpenJDK

I think of a few areas when looking at Microsoft Build of OpenJDK. The first is what is your cost to run for your intended product or project, if you are strapped and fall within the supported areas of Microsoft Build of OpenJDK then it's a no brainer, Microsoft Build of OpenJDK is for you! Lastly, I think of support in the respect to running into a wall and needing a fix. It can take a while for open source tools to produce fixes that the community warrants, so again if you aren't strapped for time and haven't run into a wall and could afford to wait for fixes or relevant patches then again Microsoft Build of OpenJDK is for you. Not everyone has this luxury, but these are a few areas to think about.

Incentivized

• Support for the Java libraries that are common use today
• Support for various architecture environments - Mac, Windows, Linux, etc...
• Provides a low cost or rather no cost alternative

Incentivized

• Since it's open source, enterprise support is less than as if you are running paid like an Oracle JDK.
• Performance is improving and is I would say on par with paid solutions, this could improve to help with growth.
• Stability will happen over time with more contributions and fixes

Incentivized

Microsoft Build of OpenJDK stacks up against Oracle JDK (paid) very well. From both a performance, implementation, library support, and collaboration aspect.

Incentivized

• No cost alternative to paid JDK platforms
• Performance is that of paid JDK platforms in my opinion
• Community contribution is a bonus for contributed code and open collaboration

Incentivized