3 ms·
> The last 1%, jumping to java is not a big difference That's where you're wrong, kiddo.
by _pmf_ 5y ago
> The last 1%, jumping to java is not a big difference
That's where you're wrong, kiddo.
- BiteCode_dev 5y agoOh, I'm afraid I can't claim that sobriquet anymore unfortunately. But that's not the point. The point is that, for the 99%, staying on a slower language is ok. For the last 1%, I'll skip Java and go to Rust/Go. If I have to do a rewrite for perf sake, I'm not going to go half way.
- bjourne 5y agoBut you are not going to get higher performance in Rust/Go.
- BiteCode_dev 5y agoRust can literally contain inline asm so yes, you will. But even without that, the startup time is always going to be faster. And for IO, you will get faster perf in Go more easily. Sure, you can finely tune your Java code to get there, but it's a lot harder. It in both cases it will eat up way more memory. There is a reason Google, that did use heavily Java internally, is now moving to Go, a language they custom designed for concurrency.
- jvolkman 5y agoI wouldn't say Google is really "moving" to Go. It's an option, but plenty of projects new and old continue to choose Java.
- kaba0 5y agoWell, project loom will make the JVM arguably a better platform for concurrency. Basically every language is more expressive there (even Java), GC is much much better - in benchmarks it is not as obvious only because Go avoids creating garbage most of the time, but it can’t always be avoided; and the platform is incomparably richer on the JVM side.