Nah, it craps all over site operators for their lack of "forethought".
Oh, you didn't perfectly lay out your URIs in the initial design? Too bad, you're saddled with the unending burden of maintaining redirects forever or you're not "cool". Should have known the company was going to move to Markdown static site generation five years before Markdown was invented.
Miss me with that shit. Link rot is the burden of the link author, not the target.
Supporting redirects can be simple, depending on your SSG (and it's possible to make extensions to most of them, so this could be something that responds to a posts frontmatter). It could just generare an html file with this
<meta http-equiv="refresh" …>
sent in the head, and some html/css to make it pretty. It's not ideal, but I assume search engines support it (dunno if there's any additional SEO improvements).
> the unending burden of maintaining redirects forever
Right because keeping a list of source->destination and configuring your current server based on that is such a burden...
> Miss me with that shit. Link rot is the burden of the link author, not the target.
The link author isn't the one making the changes, the target is. The link author might not even be alive anymore. Expecting others to untangle your mess is ... not cool.
> Should have known the company was going to move to Markdown static site generation five years before Markdown was invented.
Okay, but you did know, right? Maybe not that the new thing would be called Markdown or exactly when but that there would be a new thing. The W3C sure knew and told you. That's why they wrote e.g. this paragraph:
> Software mechanisms. Look for "cgi", "exec" and other give-away "look what software we are using" bits in URIs. Anyone want to commit to using perl cgi scripts all their lives? Nope? Cut out the .pl. Read the server manual on how to do it.
Oh, you didn't perfectly lay out your URIs in the initial design? Too bad, you're saddled with the unending burden of maintaining redirects forever or you're not "cool". Should have known the company was going to move to Markdown static site generation five years before Markdown was invented.
Miss me with that shit. Link rot is the burden of the link author, not the target.