Except now you can't update the contents of a page not even one tiny bit without also changing its URL, which is equally useless.
While I concede that the ability to retrieve the previous version of a page by visiting the old URL (provided anybody actually still has that old content) might come in handy sometimes, I posit that in the majority of cases people will want to visit the current version of a page by default. Even more so, I as the author of my homepage will want the internal page navigation to always point to the latest version of each page, too.
So then you need an additional translation layer for transforming an "always give me the latest version of this resource"-style link into an "this particular version of this resource" IPFS link (I gather IPNS is supposed to fill that role?), which will then suffer from the same problem as URLs do today.
a content-derived uri is a necessity for some things (indisputable facts, scientific papers, opinions at a moment in time, etc.) but foolish for others. Think of a website displaying the current time or anything inherently mutable.
But having unchanged documents move to new locations on the same domain without a redirect but a 404 is just utter unforgivable failure. Or silently deleted documents, also an uncool nuisance.
Both happen a lot. That's what comes to my mind, when I read the initial quote.
Me updating page contents happens (relatively) often. Me re-working my whole page structure which would break existing conventional URLs happens very rarely.
Because conventional URLs don't care about updates to a page's contents, this means the common case of only updating pages requires no additional configuration. I only need to invest additional time setting up redirects on the rare occasion that I actually do re-arrange file names etc.
IPFS URLs on the other hand are revision-specific, so they break (or rather actually get out of date and eventually break if at some point in the future nobody has a copy of that version cached/pinned somewhere any more) as soon as I fix even one tiny little typo, so I need to set up some sort of URL mapping service right from the start.
While I concede that the ability to retrieve the previous version of a page by visiting the old URL (provided anybody actually still has that old content) might come in handy sometimes, I posit that in the majority of cases people will want to visit the current version of a page by default. Even more so, I as the author of my homepage will want the internal page navigation to always point to the latest version of each page, too.
So then you need an additional translation layer for transforming an "always give me the latest version of this resource"-style link into an "this particular version of this resource" IPFS link (I gather IPNS is supposed to fill that role?), which will then suffer from the same problem as URLs do today.