Re:Go: What We Got Right, What We Got Wrong
by didntcheck on Friday January 05, 2024 @04:54AM
(#38877370)
The performance of the JVM was definitely a fair criticism in it's early years, and still is when writing performance-critical applications like databases, but it's still possibly the fastest managed runtime around, and is often only a margin slower than native code on hot paths. It seems the reputation has stuck though, to the point that I've seen young programmers make stock jokes about Java being slow when their proposed alternative is Python
[ Parent
| on HN ]
Re:Go: What We Got Right, What We Got Wrong
by kaba0 on Friday January 05, 2024 @02:42PM
(#38883779)
Just for an example: on the recent 1billion rows challenge, the top java contender takes only 2x as much time as a SIMD-optimized C one.
Re:Go: What We Got Right, What We Got Wrong
by grumpyprole on Saturday January 06, 2024 @04:40PM
(#38895780)
Yes it's possible to write Java without any boxing of primitives or garbage collection, but one can't use any of the standard libraries and it's not really Java one is writing but a very restricted subset. I don't think these benchmark are particularly indicative of real world performance. But of course Java is still hundreds (thousands?) of times faster than Python.