3 ms·
Likely because they are a Java shop. All the IDEs they develop use Java, so they have quite an expertise in low level optimization for this language.
by rednb 3mo ago
Likely because they are a Java shop. All the IDEs they develop use Java, so they have quite an expertise in low level optimization for this language.
- jonathanlydall 3mo agoThey also have C# expertise, but yes, Java is probably the language they have the most expertise in.
- rob74 3mo agoThat's true, although, if you look at them, you wouldn't notice. The only mention of JVM you can see in the IDEs is in the About dialog, and the IDEs install and run their own OpenJDK, so no JVM has to be installed globally. Almost as if they were a bit self-conscious about using such an "unsexy" architecture...
- mike_hearn 3mo agoBundling a JDK with the app is the officially sanctioned way to ship Java apps since Java 9, so for over a decade now.
- Hendrikto 3mo agoThe JDK is too big for every app to do that, imo.
- pjmlp 3mo agoWhich is why there are linking and packaging tools for trimming fat that isn't needed, or even AOT compile the application.
- well_ackshually 3mo agoYou mean a JRE, because the whole JDK contains a bunch of things you're never going to need. Mind you, a default JRE redistribution makes your app at least 100+MB. Using jdeps to strip out unneeded things is a good idea if you want it to get down to 25 ish MBs.
- jamesfinlayson 3mo agoJREs haven't been a thing in like a decade I thought.
- well_ackshually 3mo agoYeah, saying JRE is a bit of a shortcut since you're supposed to jlink & jpackage & jdance &jpray to get a slimmed down JVM released with your app, but it's closer to what would be a JRE than a full JDK