10 ms·
It's not like PL/I didn't allow for similar flaws, so "Worse is better" is neither here nor there. At least C was simple enough to learn for most programmers.
by zozbot234 3y ago
It's not like PL/I didn't allow for similar flaws, so "Worse is better" is neither here nor there. At least C was simple enough to learn for most programmers. It's still generally the case that a simple approach is more likely to be correct than an overly complicated one for which it's not even clear what "correct" means.
- musicale 3y ago> It's not like PL/I didn't allow for similar flaws, so "Worse is better" is neither here nor there. PL/I is one of the reasons that Multics was not plagued by buffer overflows: "The net result is that a PL/I programmer would have to work very hard to program a buffer overflow error, while a C programmer has to work very hard to avoid programming a buffer overflow error." [1] [1] P. Karger, R. Schell, "Thirty Years Later: Lessons from the Multics Security Evaluation"