3 ms·
One of the issues I see with C is that there is a core set of C developers that sees C as the only systems language, being "just" a portable assembler, and if y
by jcranmer 7y ago
One of the issues I see with C is that there is a core set of C developers that sees C as the only systems language, being "just" a portable assembler, and if you're not good enough to avoid these pitfalls in C, you shouldn't be programming it. And, as you allude to, I suspect that many of the people with different viewpoints have moved on from the language, leaving this conservative C core in charge of language evolution design.
- quotemstr 7y agoI'm reminded of hand-washing in medicine. Even after it became indisputable that hand-washing improved patient outcomes, doctors didn't want to do it: they felt insulted by the implication that their hands weren't already clean. The truth is a doctor could be the most hygienic person in the world and still walk into a surgery with germ-coated hands. A hand-washing requirement isn't a personal insult: it's just a reflection of reality. But pride gets in the way. Likewise, even if you're the best programmer in the world, if you write a large C program, sooner or later, you're going to introduce a security vulnerability. Switching to a safe language isn't an admission of some personal inadequacy: it just reflects how the world works. But pride gets in the way.
- coretx 7y agoPeople should also not forget that the C culture comes from a age when the philosophy of letting your executable be as simple as possible, do only one thing and do it perfectly & interoperable was so prevalent it did not need discussion. It's a much different ecosystem compared to today; thousands of abstractions, tons of includes, unknown functions etc. In one environment it's "ok" to make "a" mistake, in another it ain't.