Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

C/C++: You spend 45% of development time fixing memory bugs.

Rust: You spend 45% of development time fighting with borrow checker/Rust syntax.

GC-based languages: You spend those 45% for anything else you like...



Generally the later you detect the bug, the harder it is to fix.

If it doesn't compile, you have to fix it, probably right after you finished typing it. You still have the overall idea of what you were doing fresh in your mind.

If it compiles and then something weird happens a week later, you may spend days trying to reproduce it, then you'll have to pull out valgrind/ASAN, look at the dumps of that, figure what the hell does it mean that something goes wrong in the bowels of the STL/some other library, then backtrack from there to where that interacts with your code, figure if it's indeed a you problem or a library problem, remember again what this weird code is supposed to be doing, then finally fix, and do testing.


> Rust: You spend 45% of development time fighting with borrow checker/Rust syntax.

Only a beginner. I spend practically no time fighting the borrow checker because I figured out how to structure my code to not have issues.


GC-based languages: outsource 45% to the user.


Bloated software is not a problem at all...




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: