4 ms·
Sort of a bullshit reason. Too expensive to "bring the infrastructure and code in line with modern standards." What does that mean? Why is it necessary to do th
by ams6110 9y ago
Sort of a bullshit reason. Too expensive to "bring the infrastructure and code in line with modern standards." What does that mean? Why is it necessary to do that at the expense of shutting down the service?
- reificator 9y agoMajor security or stability bugs resulting in increased operational costs over time? Ones that are difficult to fix with the current infrastructure and codebase?
- deleted 9y ago[deleted]
- barrkel 9y agoOp-ex exceeds revenue to the point that operating capital is better invested elsewhere. Some things possibly adding step changes to the costs can be regulatory (GDPR) and patching (outdated dependencies having no obvious upgrade paths). The latter is a killer, especially if it's a platform going away, eg some LTS OS.
- jacquesm 9y agoWhat it means is that they have let their technical debt accrue to the point where they feel the only way forward is too costly to justify the work. It happens to 'cash cows' that are only milked but not fed. Eventually the cow dies of malnutrition.
- user5994461 9y agoFrom my understanding, the code is lost or there is noone who knows how to run the software or the infrastructure. These are real problems that can kill a company. The only resolution is to rewrite or reverse engineer everything, not an option for old software with little revenues.
- keerthiko 9y agoThey are declaring technical bankruptcy.
- paxys 9y agoWhy is that bullshit? They're saying that the site is too expensive to run as-is and too expensive to fix. That's pretty much the most obvious reason possible.
- ams6110 9y agoThey're not saying that though. They make a hand wavy statement about "modern standards" and try to imply that it's not their fault. If they had just said "the business is no longer profitable" I wouldn't have a complaint.