3 ms·
So I'm aware of at least BBC using this approach, where opening really old articles reveals they have their 90s site still up. I'm also aware of at my last empl
by Macha 6y ago
So I'm aware of at least BBC using this approach, where opening really old articles reveals they have their 90s site still up. I'm also aware of at my last employer, an unmaintained wiki with open security issues that nonetheless had vital information for still in use legacy internal software was replaced by saved static HTML grabs so the information wasn't lost.
But for a lot of medium sized companies with dynamic websites, this isn't always practical. They may not have the know how to dump their 2000s drupal install to static HTML files, and don't have the IT staff to upgrade and secure it.
- WJW 6y agoI wish people would would change their language regarding tech debt. The companies of your second paragraph choose not to upgrade and secure their websites. It's not something unavoidable.
- indigo945 6y agoThey point your parent poster is making is that these companies instead choose to shut the website down, which is a legitimate alternative to updating and securing it -- unlike just leaving it up without maintenance, which is not.
- WJW 6y agoThat's why I specifically indicated the companies referred to in the second paragraph of the parent post. The BBC and the unnamed company where Macha was working did it correctly.
- jpswade 6y agoThe BBC's approach to this has so far worked out as the best here and continues to provide its the correct approach. I think there's always been a lot to be said for good, static sites, and there still is.