What about an IDE? Is there an IDE?
GraalVM is just Java :) you don't need a new IDE.
GraalVM
101–108 of 108 posts
Re: GraalVM
#102Earlier 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.
Re: GraalVM
#103Check out babashka, a Clojure interpreter with instant startup, running in a GraalVM-compiled binary: https://github.com/borkdude/babashka
Re: GraalVM
#104Earlier 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).
When you give back your improvements to the community, under any license, you free yourself from maintaining a separate fork.
Re: GraalVM
#105Re: GraalVM
#106Earlier 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…
Re: GraalVM
#107Earlier 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?
Re: GraalVM
#108Earlier 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).