Earlier quoted context omitted.
Well, it does "route around damage", but there's a difference between an infrastructure damage (be it a denial of service, or a tactical nuclear strike) and a continuous, intentional action of a sentient adversary. Unfortunately, conflating those two concepts is a common mistake when designing or thinking about systems.
TBH it's mostly about the fact that the "route around damage" really applies only to a very small stack. What does the browser do, to "route around damage"? What does a DNS client do? Very little, if anything. They were not built to "route around damage", they were built to do client/server.
Browser doesn't - user does.