4 ms·
50 years of widespread C usage has shown that just trying writing without errors using C doesn't work. But surprisingly some people still believe it's possible.
by Panzerschrek 10mo ago
50 years of widespread C usage has shown that just trying writing without errors using C doesn't work. But surprisingly some people still believe it's possible.
- uecker 10mo agoWriting without errors using other languages also doesn't work. And if you go towards formal verification (which also does not completely avoid errors), C has good tools.
- Panzerschrek 10mo agoBy using a better language you have no errors typical for C which usually require debugging. Logical errors may still happen, but they are easy to identify without even running a debugger.
- uecker 10mo agoFor your comments I get that you drank the Kool Aid, but I see no argument.
- lelanthran 10mo ago> 50 years of widespread C usage has shown that just trying writing without errors using C doesn't work. Millions upon millions of C code, over decades, controlled (and still control) things around you that would kill you, or similar catastrophic failure. Cars, microwaves, industrial machinery, munitions, aircraft systems ... with so few errors attributable to C that I can only think of one prominent example. So sure, you can get bugs written in C. In practice, the development process is more important to fault-reduction than the language chosen. And yes, I speak from a place of experience, having spent considerable parts of my career in embedded systems.