News for hackers. Stuff that matters.
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.
Re:Go: What We Got Right, What We Got Wrong by kaba0 on Saturday January 06, 2024 @05:17PM (#38896092)
It’s okay to do some allocations - it can be stack replaced, and even if it’s not, the cost is very negligible. The problem is mindless allocation, not allocation itself.