3 ms·
For my part the problems with the JVM are manifold: - it’s a heavyweight blob that you have to ship with your binary. It can be many times the size of the thin
by doctor_eval 4y ago
For my part the problems with the JVM are manifold:
- it’s a heavyweight blob that you have to ship with your binary. It can be many times the size of the thing I’m trying to run.
- it’s a word salad of technologies that apparently I’m supposed to care about
- many of the claims of how great it is are really just ongoing claims of how great it’s going to be.
To the latter point, value types (discussed in this thread) have been discussed since I was still using Java - a quick Google shows results from 2014. I haven’t written Java code commercially since 2018. I can’t find anything suggesting it’s here yet.
Keeping track of all these technologies and trying to understand when they will arrive and make my day to day life better was a nightmare.
Compared to that, I can build a Go binary, scp it to some machine and run it. That’s not possible in the JVM world, at least not without a level of calisthenics I’m simply no longer willing to deal with.
GraalVM and friends may be wonderful technologies, but honestly I don’t care. I don’t want to have to thread the needle of this ecosystem every time I have work to get done.