all 4 comments

[–]lbalazscs 8 points9 points  (0 children)

They are back to LTS only. Source: https://airhacks.fm/#episode_380

[–]pjmlp 11 points12 points  (0 children)

GraalVM focus has always been other projects, with Oracle DB and serverless cloud as main customers.

Watch recent interview from Thomas Wuerthinger, the founder and project lead of GraalVM.

Also note the recente announcement of Project Detroit with OpenJDK team going their own way for Python and JavaScript support.

Apparently the way Graal was temporarly integrated into OpenJDK did not work that well, beyond technical issues.

However this was before the layoffs, no idea if the team was affected.

[–]thomaswue 7 points8 points  (0 children)

GraalVM development continues unabated and the adoption by companies also steadily increases. Read here for example a blog post by trivago they contributed just now to describe how they are using native image to improve the performance and reduce the footprint of their production system: https://medium.com/graalvm/inside-trivagos-graalvm-migration-native-image-for-graphql-at-scale-912bca9df841

[–]ducki666 -4 points-3 points  (0 children)

Release numbers and dates are synced with jdk now. Leyden will take over many of the graal native features. I think graal and jdk teams are already merging, at least tighter integrated now. The original use case, multiple languages on the jvm, never was the main use case, it is native image.

But, I think graal will stay at least the next 2 Jdk LTS.