Re:Rust Is Hard, Or: The Misery of Mainstream Programming
by crabbygrabby on Friday June 03, 2022 @02:56PM
(#31612250)
That is an option, or if you don't want to deal with a GC because it's eating 70% of your clock cycles under load you can use rust get performance gains and still be writing safe code...
[ Parent
| on HN ]
Re:Rust Is Hard, Or: The Misery of Mainstream Programming
by adgjlsfhk1 on Saturday June 04, 2022 @01:39AM
(#31617345)
if your GC eats 70% is your clock cycles, your language has a broken GC. in modern Java/C#, GC time is rarely more than 10%
Re:Rust Is Hard, Or: The Misery of Mainstream Programming
by nimrody on Sunday June 05, 2022 @02:54PM
(#31633807)
To get to a low GC overhead in Java (and perhaps other languages too) you have to pay with an increase in memory consumption. Sometimes as much as 100% additional RAM to avoid frequent full GC scans.
Re:Rust Is Hard, Or: The Misery of Mainstream Programming
by adgjlsfhk1 on Monday June 06, 2022 @01:19AM
(#31637431)
That's true, but malloc/free based systems also have a relatively high memory overhead due to fragmentation and programmers being worse at inserting frees than the GC. It's not at all clear that the C/C++ model of memory management has lower than 100% overhead for long running programs.