Why Was "Traditional" rmtree() Given Superpowers? (continued 2)

• So at very point when rmtree() acquired its superpowers, the dangerousness of those superpowers was recognized

• But those dangers were implicitly minimized by phrase "in situations where security is an issue".

• Responsibility for coping with that dangerousness was shifted from the maintainers of File::Path to its users

  • Users were told that security required:

    • Using a non-default syntax

    • Jump through $SIG{__WARN__} hoops