3 ms·
> That's interesting! May I ask how it works? Does that also happen with e.g. IntelliJ? Byte ranges request do most of the heavy lifting, data is loading exclu
by apignotti 1y ago
> That's interesting! May I ask how it works? Does that also happen with e.g. IntelliJ?
Byte ranges request do most of the heavy lifting, data is loading exclusively on-demand.
> Doesn't the JVM run everywhere in 2025?
What about iOS? Android has Java, but can't run desktop Java apps. Chromebooks also have limits.
- palata 1y ago> Byte ranges request do most of the heavy lifting, data is loading exclusively on-demand. I don't understand what that means. The JVM is supposed to interpret and sometimes compile bytecode, right? How can it be done with only a fraction of the JVM? Or are you saying that it is constantly communicating with a server that does the work?
- apignotti 1y agoThe VM itself is very small, it's the OpenJDK runtime that is quite sizeable. Byte ranges are used to only download the parts of the runtime (in terms of bytecode) that are required. There is no server-side computation. CheerpJ runs code exclusively client-side.
- palata 1y agoBut you said before that you only download a subset of the JVM, right? Or did you mean a subset of the JDK, including the JVM and... I guess other stuff?
- apignotti 1y agoI meant the JVM in an extended sense: the combination of the bytecode parsing, JIT compiler and OpenJDK runtime. You are right, I should have been more precise and refer to only the runtime part, which is by far the most significant.
- palata 1y agoI was not trying to prove you wrong, I'm just genuinely interested :-). I don't see a lot of articles about the JVM these days.