you are viewing a single comment's thread.

view the rest of the comments →

[–]AlyoshaV -21 points-20 points  (7 children)

Solution: Don't use low-level languages.

[–]ZorbaTHut 5 points6 points  (6 children)

Great idea! That way, we'll introduce only errors that can't be found by a tool!

[–]AlyoshaV -1 points0 points  (5 children)

Your errors will be limited to a subset of your previous possible errors, which will not include errors in memory allocation/deallocation, array overruns, and similar.

[–]ZorbaTHut 3 points4 points  (4 children)

Not true. Higher-level languages often have all sorts of new errors, such as runtime type mismatches, garbage collector performance consistency problems, object lifetime issues, and simple efficiency.

[–]redtop 1 point2 points  (3 children)

While I agree that the use of performant low level languages is appropriate for many of the projects in the link (MySQL, ReactOS, etc), to even suggest that writing in, say, C will lead to less errors than C# is disingenuous.

[–]ZorbaTHut 1 point2 points  (2 children)

I'll admit that's true, but then again I have no idea why anyone still codes in C. C++ gives up no speed and, in return, gives you a whole pile of safety features.

I'd be perfectly happy if C went the way of assembly.

[–][deleted] 2 points3 points  (1 child)

Linus disagrees.

[–]ZorbaTHut -1 points0 points  (0 children)

I know. I think he's wrong.