I saw a comparison claiming a Java port of a Rust word processor was faster, smaller, more portable, and used less memory. How much does that tell us about the languages, and what does more native mean here?
Does this Java word processor port show Java can outperform Rust?
Answers
It tells you something about those two implementations, not that Java is generally faster or smaller than Rust. A port can change algorithms, libraries, UI frameworks, and a lot of other details besides the language.
For a useful comparison, I would want the same features and workloads, the build settings, and separate measurements for startup, editing responsiveness, memory, and packaged size. A reverse port from Java to Rust could be interesting too, though it would still be just one pair of implementations.
Reply to this answer
More native here seems to mean OS integration, not that Java somehow becomes a more native language. The examples given were native menus, drag and drop, and copy and paste. Those are useful things to compare, but they depend heavily on the UI toolkit and platform support.
Reply to this answer
The runtime details matter. The comparison used ParparVM, an ahead of time Java VM, rather than a conventional just in time JVM. The Rust build reportedly used the project's release profile with O3 optimization. That gives some context, but it does not establish whether either implementation was well optimized or whether the measured tasks were equivalent.
m.826!gasketpocket:
So the Java result should not automatically be read as a typical JVM result either?
Nexravi+3m:
Exactly. The runtime and packaging choices belong in the description of the result.
Reply to this answer
There is also a quality question. If the original app is rough or its code is inefficient, beating it may not take much. That does not make the port useless, but it makes it a weak basis for a broad language comparison.
AI-assisted porting adds another variable if it was used. It might introduce problems or make optimizations along the way, so the generated code still needs scrutiny.
Reply to this answer
I would focus on what you need from the application. Java is a viable choice for desktop software, and Rust has different runtime and memory management tradeoffs. Neither a garbage collector nor its absence settles the memory usage of a particular app on its own.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Neravik.9m:
Right, and if the port got extra optimization work, that needs to be part of the comparison rather than treated as a language advantage.