Re:Apache Helix – Near-Realtime Rsync Replicated File System
by echelon on Monday October 26, 2020 @07:55PM
(#24903007)
Which is a breeze. You solve it when writing the program. Not at runtime in some mysterious JVM pause death spiral.
[ Parent
| on HN ]
Re:Apache Helix – Near-Realtime Rsync Replicated File System
by uglycoyote on Monday October 26, 2020 @08:53PM
(#24903409)
I dunno, I work in C++ in games and we spend way too much time thinking about how to manage memory. It's not a breeze at all.
Re:Apache Helix – Near-Realtime Rsync Replicated File System
by cle on Monday October 26, 2020 @10:05PM
(#24903854)
You would do that even with a GC language like Java. The serious performance code paths in Java also do meticulous memory management to minimize allocations, GC costs, and utilize off-heap memory (Netty comes immediately to mind).
In my opinion it’s the worst of both worlds at that point—you’ve got to manually manage memory and tip toe around the runtime.
Re:Apache Helix – Near-Realtime Rsync Replicated File System
by echelon on Monday October 26, 2020 @09:11PM
(#24903522)
You're not wrong, but that's a bit of an unfair comparison.
You're likely talking about work on custom memory allocators and impact on real time performance. In the hosted services domain this isn't so much an issue. Nobody's doing that in Java, and you likewise wouldn't care much if writing the same type of service in Rust.
Rust very much enables you to write high level, Java-style code. It's not bad code, nor is it difficult to write.