Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

And it seems to be working on Graal, though people are trying to find a way around limitations related to reflection, so I understand.


sort by: page size:

They are also working on graalvm compatibility, as of late July.

What motivates you to use reflection so much? I just don't use reflection with GraalVM and it works fine.

There's two pieces to GraalVM:

1. The new JIT

2. The Native Image, AOT

Reflection is an issue for (2), not (1).


Reflection only matters if you are using graal for AOT. It's still a full JVM.

My (admittedly not huge) experience with Quarkus would tell me that GraalVM is nowhere near ready, most specifically because of reflection.

That's interesting, would love to read more (blog post maybe?) on issues with GraalVM.

Well this is interesting.

I've been following GraalVM for a long time now and this looks like a very "possible" project.


What's your view on Graal? Is that making headway on de-fluffing and robustifying the code or does this not really tackle the issues you had in mind?

Graal itself still has limitations with many libraries yet, the biggest one being having any library that heavily uses reflection. I'd look at some of the work red hat is doing with some of its java libraries and quarkus: https://developers.redhat.com/blog/2019/03/07/quarkus-next-g...

There are good frameworks that already work well with GraalVM native, including Quarkus and Micronaut. They avoid reflection altogether in most cases.

Ah right you are, and I've only experimented with Graal to build native images.

FWIW Graal is probably one of the most exciting technologies to come out of Oracle in a long time.

ah this is great. I need to look at switching to Graal.

I don't think I'm familiar with this (I may have come across it but didn't identify it by name when I worked with Graal?), could you provide a link? :o Thanks!

please provide substance, this mere dismissal seems ungrounded, GraalVM native in most cases just works(tm). There is some config if you make heavy use of reflection and that is pretty much all.

I haven't touched GraalVM in a couple years, but the big-ish project that I did with it in Clojure was mostly painless, except for the fact that I had to use type-hinting a lot more frequently, due to the reduced reflection capabilities of GraalVM.

Other than that, it was actually very pleasant.


Its more symmetry with Graal.js

I see. GraalVM sounds great. Thanks for the explanation

I guess that's the point of Graal VM, right?
next

Legal | privacy