3 ms·
At the end of the day, it's simply an unrealistic expectation that URIs don't change. And declaring for 20+ years that this isn't "cool" isn't going to change a
by crazygringo 5y ago
At the end of the day, it's simply an unrealistic expectation that URIs don't change. And declaring for 20+ years that this isn't "cool" isn't going to change a thing about it...
The web is dynamic, not static. Sites come and go, pages come and go, content gets moved and updated and reorganized and recombined. And that's a good thing.
If content has moved, you can often use Google to figure out the new location. And if you want history, that's what we fortunately have archive.org for.
For any website owner, ultimately it's just a cost-benefit calculation. Maintaining old URIs winds up introducing a major cost at some point (usually as part of a tech stack migration), and at some point benefits from that traffic isn't worth it anymore.
There's no purist, moral, or ethical necessity to maintain URIs in perpetuity. But in reality, because website owners want the traffic and don't want to disrupt search results, they maintain them most of the time. That's good enough for me.
- rimliu 5y agoIt is very sad that this "cost-benefit" calculation ends up ruining the web. Devs too lazy to learn the basics and doing everything with React and a gazzilion of libs, nobody caring about accessibility, nobody caring about the url structure. It is very possible to go through 50 CMSes and still keep the URLS intact. Just that we forgot the users and UX moved away giving up the place for the DX. I still hope for the new web standards revoliution. Zeldmans of XXI century, where are you?
- prepend 5y ago> it's simply an unrealistic expectation that URIs don't change. I disagree. If I generate urls systematically, then when I change the scheme I can easily send a 302 with the new url. It’s also not hard to just keep a mapping table with old and new. I think that it’s lazy programmers who can’t handle it. Or chaotic content creators. I’ve had many conversations with SharePoint people who frequently change urls by renaming files and then just expect everyone linking to it to change their links. They seem to design content without ever linking because links break so much. It’s the damndest thing as it makes content hard to link to and reuse. People are too young to even care about links and stuff. Of course if SharePoint search didn’t suck it wouldn’t be as much of an issue.
- crazygringo 5y ago> I can easily send Honestly that's just not true. If you upgrade to a new CMS/system, the way it routes URLs can be completely incompatible with the old format and it just can't accomodate it. And if you're dealing with 10,000,000's of URL's and billions of pageviews per month, you're talking about setting up entire servers and software in front of your CMS dedicated just to handling all the redirect lookups. And you also easily run into conflicts where there is overlap between the old naming convention and the new one, so a URL still exists but it's to something new, while the old content is elsewhere. Yes it's possible. But the idea that it's "not hard" is also often very false. > I think that it’s lazy programmers No, it's the managers who decided it wasn't worth paying a programmer 2 or 4 weeks to implement, because other programming tasks were more important and they employ a finite number of programmers. For commercial websites, it's not laziness or "chaos". It's just simple cost-benefit.