Live data from Hacker News

GraalVM

graalvm.org

101–108 of 108 posts

Re: GraalVM

#101
post #33

What about an IDE? Is there an IDE?

GraalVM is just Java :) you don't need a new IDE.

But isn't it more than Java? You can run other languages like Node.js and Python besides Java. So what I'm asking for would be an IDE where I can easily program calls from Java to Node.js or vice versa, for example. Or some other poly-language IDE if such exists

Re: GraalVM

#102
post #74

Earlier quoted context omitted.

I'd like to hear about them, because apart from enterprise applications, there aren't that many left. Electron is the new desktop Java.

I wouldn't call them dominant by any stretch, but I wouldn't call them uncommon. Ones I use somewhere between daily and semi-regularly: * Pycharm * Datagrip * Charles * JDiskReport * TexturePacker * Android Studio and associated tools * Apache Directory Studio * Zed attack proxy That's just stuff that I've used recently and on an ongoing basis... I feel like I see quite a bit more of it.

I used to use a thing called JMeter. But its GUI felt inferior in my view compared to typical Windows applications.

Re: GraalVM

#103

Check out babashka, a Clojure interpreter with instant startup, running in a GraalVM-compiled binary: https://github.com/borkdude/babashka

This is a good example of where Graalvm's native image is interesting. This is a CLI tool that lets Clojure developers create scripts that are as fast as bash scripts. Clojure may well not be your bag, but stay with me - we're talking about CLI or TUI's written in Java (or a java-based language) that are easy to distribute as statically compiled binaries.

Re: GraalVM

#104
post #83
post #68

Earlier quoted context omitted.

That's the most wonderful thing of GPL'ed software - enforcing the no-selfishness rule.

GPL is nice, but it seems it's a constant uphill battle - maybe after the GPLed thing becomes the standard things become slightly easier (economically upstreaming becomes cheaper than maintaining a fork).

If you are just using the software and not selling or offering binaries, it's not a concern.

When you give back your improvements to the community, under any license, you free yourself from maintaining a separate fork.

Re: GraalVM

#106

Earlier quoted context omitted.

While what Quarkus promises sounds delightful, the actual dev experience is still not something I'd recommend. The amount of libraries one can use is still very limited. The compiler errors when one chooses to step outside of the approved list of supported libraries, are very cryptic (or non-existent). In my case, I tried to use Apache Freemarker for templating. I could've tried Quarkus' own templating library, but i…

Agreed that the experience when trying to native-enable existing libs isn't the greatest. Altough those things are rather reported by the GraalVM compiler rather than Quarkus. The working model and assumption is that somebody goes through this once and then either contributes changes to the library in question back upstream or provides a Quarkus extension for that library, sparing others from that hassle. That RAM co…

Isn't native-image memory consumption and compile time basically a known issue by the graal team?

Re: GraalVM

#107
post #90

Earlier quoted context omitted.

Most of GraalVM is open source. If anything, their biggest commercial error may be open sourcing too much. GraalVM EE is quite expensive for what it adds over the open source versions.

Is there a summary anywhere of what parts/features are and aren't open source?

Basically more performance and managed Sulong (blocks memory management errors in C/C++ you run on the JVM). And for native AOT compiled images, G1 garbage collector (which is itself open source but the integration isn't).

Re: GraalVM

#108

Earlier quoted context omitted.

Is there a summary anywhere of what parts/features are and aren't open source?

Basically more performance and managed Sulong (blocks memory management errors in C/C++ you run on the JVM). And for native AOT compiled images, G1 garbage collector (which is itself open source but the integration isn't).

The profile-guided optimization is a pretty big deal if you're concerned about performance. Based on the benchmarks I've seen, GraalVM Community tends to outperform JIT-compiled Java for applications where warm-up time is a significant portion of total run time, but JIT-compiled Java tends to outperform Graal, sometimes by a significant margin, for anything long-lived. Profile-guided optimization would theoretically close that gap.
Post reply on HN