this post was submitted on 13 Jul 2023
37 points (100.0% liked)
Java
1393 readers
3 users here now
For discussing Java, the JVM, languages that run on the JVM, and other related technologies.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
When I worked for Amazon, someone had created a command line tool to be used in builds, but repeatedly starting up JVMs is painfully slow. I rewrote the app in C++ and it could be invoked 81 times vs one invocation of Java version.
If I need speed, I'll use C++. If I need developer productivity, I'll use Ruby.
Why in the world would you rewrite it when you could take an hour and get it compiling with graalvm and it would be just as fast as c++?
Tbf he's also suggesting that Ruby is the most dev friendly language he could use, so I'm already a bit skeptical lol
I mean, I agree with them on that. It’s very dev friendly. You definitely shouldn’t be building large scale apps in it, but it’s more readable than almost every single language out there. But rewriting a whole app in a new language instead of just using the tools available to get the best of both worlds is just a bad idea.
I've never tried Graal. Is it easy to use? Like, is it a dropin replacement for javac or what?
It’s pretty easy to use. If you are using a lot of reflection you might have trouble, but if you’re using a standard large framework like spring, quarkus, or micronaut you’ll be fine. Quarkus makes it dead simple honestly. We deploy all of our Kotlin lambdas on AWS using Graal. It’s faster than node and much easier to write safe code.
And this is how people build the largest (in terms of the actual size of the binary on the disk) command line utilities in history.
I don’t know why you would think that. GraalVM can compile tiny tiny packages, and you can easily remove features from the JVM if you don’t need them. It’s a terrible myth that JVM means massive binaries.
...If you need both, you use Rust
I'm not so sure if the JVM startup was the culprit in your situation. The Computer Language Benchmarks Game shows that even for short runtimes, the startup doesn't affect their performance numbers that much
That link just compares benchmarks with and without warmup, but not without startup. The JVM's startup can take upwards of 2 seconds, depending on the program.
Oh, I'm dumb. Thanks for clearing this up :)
You hand me till "Ruby" ROFL.