undefined | Better HN

0 pointstombert1y ago0 comments

> I'm no wasm expert, but I find it just fantastically unlikely that they're going to beat the decades of research that have gone into the JIT in the JVM anytime soon

Probably not, but that's sort of orthogonal to my point.

Java started as "write once run anywhere", but it has almost become the opposite of that: "write once, run it on your specific server".

"Portability" is not nearly the same concern with Java as it was thirty years ago; I don't have direct numbers on this, but I would guess that a vast majority of Java code written in 2025 is either running on a server or running an Android app, neither of which are nearly as "portable" what was kind of promised in the 90's, at least not on the desktop.

0 comments

mdaniel1y ago

You say that, and yet for your cited Android apps, they are built using gradle, which is written for the JVM, or using Maven, which is written for the JVM, and likely even typed inside IntelliJ (aka Android Studio) which is written for the JVM. Also, this may be splitting hairs, but Android is actually dalvik, not the JVM

tombertOP1y ago

That's why I deliberately said "Java", not JVM (though I think dalvik has been deprecated and it's ART now).

I'm sure you can list any number of programs that are written in Java, but it certainly has not been the cross-platform standard that everyone was promised; it feels like Electron has more or less taken its mantle in the world of desktop land.

koiueo1y ago

> "write once, run it on your specific server".

Funny, how people forget that a "specific server" can be running Linux on bare metal ARM or a x86 container, or maybe Windows or even MacOS.

tombertOP1y ago

I guess what I'm trying to say is that you're not typically deploying JAR files outside of an extremely controlled environment.

For a server environment, I set all the parameters I want and then I code around it. Obviously there's a lot of variation between different servers, but you typically develop your server code a specific set of servers.

koiueo1y ago

And you don't have to think about your server architecture when you run unit tests on your jar locally from your M4 MacBook.

How convenient is that, huh?

j / k navigate · click thread line to collapse

0 pointstombert1y ago0 comments

> I'm no wasm expert, but I find it just fantastically unlikely that they're going to beat the decades of research that have gone into the JIT in the JVM anytime soon

Probably not, but that's sort of orthogonal to my point.

Java started as "write once run anywhere", but it has almost become the opposite of that: "write once, run it on your specific server".

0 comments

mdaniel1y ago

tombertOP1y ago

That's why I deliberately said "Java", not JVM (though I think dalvik has been deprecated and it's ART now).

koiueo1y ago

> "write once, run it on your specific server".

Funny, how people forget that a "specific server" can be running Linux on bare metal ARM or a x86 container, or maybe Windows or even MacOS.

tombertOP1y ago

I guess what I'm trying to say is that you're not typically deploying JAR files outside of an extremely controlled environment.

koiueo1y ago

And you don't have to think about your server architecture when you run unit tests on your jar locally from your M4 MacBook.

How convenient is that, huh?

j / k navigate · click thread line to collapse