sumatra

Since Sumatra depends on Graal, it being integrated, means Graal also has to be.

This is why project Sumatra is using Graal and now jRuby is also playing with it.

And project Sumatra -- while cool -- was never a big influence over OpenJDK's plans.

If you look at sumatra dev mailing list archive, you'll see the last email there states it's not in active development.

My point is that Sumatra wouldn't have played a significant role in the decision of when to make Graal HotSpot's default JIT.

If an office-suite is not your speed, Sumatra PDF exists, and is free, open, has no bundling, and is available in a portable flavour.

I was replying to pjmlp's comment: >Maybe with Sumatra the integration would be deeper than just an API, e.g.

Maybe with Sumatra the integration would be deeper than just an API, e.g.

I know, but I imagine it will only be fully merged if Project Sumatra turns out to be integrated.

Programs like Evince (Poppler) and Sumatra have come a long way.

They've already started the process with Sumatra or without.

But why would graal depend on sumatra for integration?

Here's a TL:DR for you: "The analysis presented in this paper indicates that MH370 changed course shortly after it passed the Northern tip of Sumatra and travelled in a southerly direction until it ran out of fuel in the southern Indian Ocean west of Australia.

BTW, you don't even need Graal to be the default JIT in order to support Sumatra, anyway.

The interesting thing is, about 75 thousand years ago is humans were almost wiped out complete when the Toba supereruption happened in Sumatra.

Sumatra was about GPU offload, not so much metacircular JVM.