Hacker News new | past | comments | ask | show | jobs | submit login

His point is correct. To pretend to make Cpp safe, you need google sized budget (if not in engineering, in marketing, but oh well)



ELI5: as far as I know, „safe“ programming languages are able to avoid memory related issues that are/were prevalent in C(++). Is this actually the class of bug that causes most security related issues in the browser?


Yes, memory safety issues make up a large majority of high-severity security bugs in Chromium. See https://www.chromium.org/Home/chromium-security/memory-safet...


How do you carry water in a sieve? That's the personnel cost analogy to have safe cpp. His point is not about replacing the sieve, it is about having the money to still have some water across even when using sieves.




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

Search: