> 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

> 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"