I would estimate that the number of programs it breaks in the world will be less than 10. As long as one of those 10 isn't CGI.pm, we're probably okay.
About this quote
- What does it mean?
- Wall estimates few programs will break due to Perl, and as long as CGI.pm isn't among them, it's acceptable.
- In plain terms
- Only a few programs will break; avoid breaking CGI.pm.
- What can you take from it?
- Limit impact of changes, especially on critical modules.
Where it applies
Putting it to work
Questions to consider
- What tests ensure minimal breakage?
- How to prioritize critical modules?
Another view
The estimate is informal and may overlook broader effects.
More from Larry Wall
Perl should remain fast and intuitive (to the extent that it is :-)
Permalink to quote #187 Just put in another goto, and then it'll be readable. :-)
Permalink to quote #189 That's a valid argument. I just don't think it's valid enough. :-)
Permalink to quote #186
Related quotes
Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. Basically, a lot of the problems that computing h…
Alan KayAlan Kay quote #8 Is it possible that software is not like anything else, that it is meant to be discarded: that the whole point is to always see it as a soap bubble?
Alan PerlisAlan Perlis quote #15 In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people.
Linus TorvaldsLinus Torvalds quote #22