Hacker News Reader

Comment by 1over137 | Hacker News Reader

No one is smart enough to write bug free in any language.

This is the reason why performant and "safe" systems languages are on the rise and being accepted into foundational areas of our operating systems (such as the kernel). When the attack defense surface is tighter (language, tooling, compiler instead of the actual code itself), the smart folks can stay at that layer, while the masses can write more code at a level of abstraction that nullifies many of these vulnerabilities by default.

The difference is that C casually makes common everyday bugs into security vulnerabilities.

I can't find it now, but I heard that NASA developed processes to produce completely error-free code (for the moon landings iirc). The problem is that it's incredibly time consuming and expensive to do.

Like everything in CS, apparently this is a trade-off, not an absolute. You can get bug-free code, but it's not commercially viable and is extremely tedious to do.

It’s probably about how they write the space shuttle software, and it’s quite a famous article. The original is now paywalled but there are many copies.

https://www.eng.auburn.edu/~kchang/comp6710/readings/They%20...

This is example of what I call "the tipping paradox", and I'm almost sure that this phenomenon has its own proper scientific name.

When asked, people prefer €15 burger no tip, but when actually making a choice, they prefer €10 burger with €5 tip. Similarly, companies state "bug-free code" as a goal or requirement, but then they prioritize other goals over code correctness. My workplace is in the process of completely removing code reviews. And actually, I don't disagree with the decision - my career is short, but I have never seen reviews fulfill any purpose other than to share the blame in case of an incident.

They are removing reviews or just human reviews? It’s interesting and I kind of agree to a certain point that human review is not the best way to find and fix bugs. We’ve had so many bugs in code that was fully reviewed by at least 2 humans. Ai review is clearly superior. Human reviews main purpose to me right now is to spread know of what is being worked on.

That's why we designed better languages that can block the compilation if memory hasn't been handled properly.

Clearly it’s because people never got the memo: https://www.rfc-editor.org/rfc/rfc9225.html

Reply on news.ycombinator.com