Microsoft Build of OpenJDK vs. GraalVM

Microsoft has contributed to the OpenJDK project and has also been able to develop support for the Mac M1 chipset. This is amazing that they've seen the importance of supporting all silicon in the spirit of Java. This is very commendable from the tech titan and we look forward to more improvements and enhancements.

Incentivized

If you want to have a cool VM, don't spend too much memory and mainly being multilanguage go ahead. Be aware there are some points that can be improved like a couple of languages are not accepted so far. Like used to, it's easy to use and you can find a lot of information regarding the tool so if you need to do something fast, it's a good choice.

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

• Best performance of applications
• High efficiency of applications
• Reduced hardware requirements
• Lesser consumption of resources
• Universal support to multiple programming languages
• Reduced size of applications
• Creation of virtual images for testing on Android and iOS mobile operating systems
• Creation of native images
• Excellent support
• Documentations are detailed enough to learn and use easily
• Easy to use

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

• It should be possible to use GraalVM EE to distribute native images of JavaFX applications for mobile platforms, especially for Apple platforms.
• Native Images are a game changer. However, compiling complex applications can be a pain. Better support for an improved transition process are a must.

Incentivized

The support we received when porting legacy applications from the GraalVM team and community was commendable. We were able to get assistance in introducing alternatives for the libraries we were using where appropriate. GraalVM support was also able to help us with some configuration options we were stuck with for configuring deployment environments on AWS compute.

Incentivized

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

Incentivized

The reason why we had to select GraalVM one is [a] cutting-edge compiling technique, GraalVM is well operated in the Environment of Open JDK, which speeds up the execution of Java programs. GraalVM makes creating packages and native apps simpler, and this improves distribution. It also brings native image support [that] makes compilation and distribution easy and effective.

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

• Financial: Increased Java container count on the same hardware.
• Performance: Decreased cold start time for container startup.
• Training: Adopting GraalVM has a learning curve. This requires investment in time and resources. The benefits come through re-evaluating our current deployments for optimization.

Incentivized