If AMP becomes irrelevant, does this end the war against URLs? Or, with Google owning the most popular browser, does this not matter?
1. Chrome only showing the domain in the address bar
No, I doubt it'll make any difference here. Google's reasons for doing that are anti-fraud, not anything to do with AMP. And (I'll give up shouting this into the void one day, I swear) Apple did this with Safari years ago and no-one cared. It's outrage for outrage's sake.
2. The whole "web packaging" format issue
Google proposed a standard that let you "fake" the URL of a page (albeit with cryptographic signing to ensure it actually came from the right host). This might be dead in the water, yes. Mozilla and Apple already came out against it, and one the primary use cases was AMP. I doubt Google will un-implement it any time too soon, but I think it'll end up being a weird edge thing that very few people care about or use.
Which is a pity, because this could have been extended into a way to allow browsers to pin a specific version of a web app and warn the user if the server sent something different the next time they visited.
Having a TOFU security policy for web apps would have made them roughly comparable to native apps for certain threat models, especially considering that native apps often auto-update without giving the user a meaningful chance to check whether the update is backdoored.
For both web and native apps, though, it would be nice if there were independently run Binary Transparency logs published so that apps would only download an update whose source code had been publicly available (and reproducibly buildable) for some reasonable amount of time to allow an audit to occur.
There's not many issues that will gather enough reactions for Apple to ever respond. It would need to be something like removing the eggplant emoji to have anything sizeable from their perspective.
A decent amount of people cared about the move to hide most of the URL, just not enough for it to be a wide societal protestation wave.
The problem here is that google has an interest in hiding the URL other than anti-fraud. Apple isn't a major player in the internet market and they have a history of "dumbing down" features, or at least reducing their apparent complexity, to make the experience friendlier to the average user. So when Safari hid the full URL, that didn't raise many eyebrows.
Many of Google's moves in recent years, most notably AMP, appear to be part of a larger plan to make the internet require Google to function. Messing around with the URL visible in the address bar seems to fit in with this plan to reduce the average consumer's awareness of where exactly they are going on the internet.
By default (i.e. until you click the bar) only showing the part of the URL that the site doesn’t control is really good for security and avoiding phishing. Now apple.paypal.secure.wendys.scamsite.info/payus/wwwcitibank just shows scamsite.info. This is a good thing! And doubly because URL paths and fragments have been made largely irrelevant to end users as app routes.
If you're going to rant about the death of the URL you should complain to HN as well that only shows the domain next to posts.
It seems harmless to show the full URL and not bait-and-switch the text upon interaction. I don't see it as the browser's job to protect users from their incompetence.
If you care at all about the health of the web, you should support browsers in protecting users from their own incompetence. Users don't blame themselves for phishing & fraud, when it runs rampant on a platform they simply switch and the end result is that native walled gardens that do protect users win over the web. This is exactly what happened with news on the mobile web; mobile news websites got so slow that Apple & Facebook started gaining a lot of ground with completely closed & proprietary news platforms (Apple News, Facebook Instant), until Google released AMP which both helped & pressured news orgs to get their shit together on the web.
I see these kinds of features sort of like padding on football players. It enables (encourages?) carelessness. Maybe the jury is still out on the net outcome, but I'm so far away from web development and the overall ecosystem as to have no opinion.
Of course it encourages carelessness, that's what users want: they want to care less about the tech they use.They simply want the benefits of tech, not the maintenance or burden of care. It's why many prefer an iPhone that makes all their software choices for them. It's why many trust an email provider to sort & filter their email instead of doing it themselves.
>"URL paths and fragments have been made largely irrelevant to end users as app routes"
No. Some SPA scenarios, for some end users != "largely irrelevant".