Very sensible argument but I actually consider it a problem that I don't know anyone's phone number. Sure it's my fault, when my mom got a new cell number I should have memorized it. I should have my significant other's phone number memorized but I don't and I suspect she doesn't have mine memorized either. In an emergency, let's say I am an an accident and my phone is destroyed, I know a couple family members land lines who have kept the same number since I was very young. Aggressively abstracting information away to make life easier has costs.
As an addendum: OP, please explain how you shared this particular obituary.
Anyway, I think you're missing his point.
URLs will exist for a long long time, just like phone numbers.
You still share your phone number, but as soon as I get your number in my address book, I don't use your number anymore, since I'll just search for your name.
Taking a small step further, you can even share your contact using bluetooth or using bump, and I won't even have to listen or see your phone number.
The same will happen with URLs, regular users don't care about them, they google them and click on the first result, or use their bookmarks... they're just a mean to an end, you still need them to share, but it's just that blue text line...
They are dead already... We're just in denial.
Meanwhile I'm just going to finish writing my routes, because resources should have an identifier, just like my phone has a number, and my network interface has an IP address... but users don't need to know about those to be happy, it just has to be there when they need it.
I think your last sentence is dead on.
They still need to exist, they just are changing roles. Like voicemails. Or better, snail mail. Horseback riding. Whatever.
(I think we already agree.)