But the possibility of abuse may be a good reason for leaving capabilities out of other computer languages, it's not a good reason for leaving capabilities out of Perl.
About this quote
- What does it mean?
- He argues that while limiting capabilities can prevent abuse, it shouldn't be a reason to exclude them from Perl.
- In plain terms
- Removing capabilities may stop abuse, but Perl should keep them.
- What can you take from it?
- Balance security with functionality in language design.
Where it applies
Putting it to work
Questions to consider
- When is it justified to omit a capability?
- How can Perl mitigate misuse?
Another view
Trade‑offs can be complex; no one‑size‑fits‑all.
More from Larry Wall
I was about to say, 'Avoid fame like the plague,' but you know, they can cure the plague with penicillin these days.
Permalink to quote #121 Oh, wait, that was Randal...nevermind...
Permalink to quote #123 It's getting harder and harder to think out loud. One of these days someone's gonna go off and kill Thomas a'Becket for me...
Permalink to quote #120
Related quotes
> (It's sorta like sed, but not. It's sorta like awk, but not. etc.) Guilty as charged. Perl is happily ugly, and happily derivative.
Larry WallLarry Wall quote #51 Well, you can implement a Perl peek() with unpack('P',...). Once you have that, there's only security through obscurity. :-)
Larry WallLarry Wall quote #140 If you try to solve a hard problem, the question is not whether you will use a powerful enough language, but whether you will (a) use a powerful language, (b) …
Paul GrahamPaul Graham quote #5