I'm just in the process of developing a lifecycle policy, being able to cut off support for a 12 year systems would make my life much more full of joy.
I'm just in the process of developing a lifecycle policy, being able to cut off support for a 12 year systems would make my life much more full of joy.
The phrase that jumps out at me is:
> being able to cut off support for a 12 year systems would make my life much more full of joy
I think this is a nearly-poetical capturing of the core problem.
The focus is on the joy and well-being of the maintainer, not the impact to all the people who will be impacted by this change. Possibly some people rely on these devices and it adversely impact their joy and livelihood when support is ended.
This happens over and over again in tech.
> Possibly some people rely on these devices and it adversely impact their joy and livelihood when support is ended.
This happens over and over again in tech.
its true and i agree with you as a useron the other hand, some software gets harder and costlier to support the longer its out there (think spec changes, security issues, updates in law etc), and even paying a normal subscription for it can cause roi to go negative, especially when factoring in opportunity cost for a business (help the old users or spend that time/money making a new feature for the majority)
my thought on it is if its a subscription, maybe for some software, the longer someone uses the old version the subscription cost could go up slowly, or if its a one-time purchase, after x years they could just buy a support ticket or something...? for ad-supported software i have no ideas...
Try estimating doing win11 updates on a 20 year old piece of delphi spftware with hardware full go custom ASICs be expected to lsat?
Until it dies due to unintentional software or hardware defect.
NOT when it is sabotaged by the manufacturer.
The point is that e-books are basically a data format plus a reader, and if the data format hasn't changed (it hasn't) and a reader is still working, what is gained by preventing that reader from being given new data to present?
amzn doesn't have to "provide support" for old kindles, but they also don't need to prevent them from downloading ebooks.
It’s ok to stop providing updates to old software and hardware.
It’s OK to not support ancient devices when writing news software.
It’s not ok to make old devices inoperable if they are using the old software and don’t need updates.
Will my old Kindle stop being able to show me the books I bought and downloaded to it? Or will it become impossible to buy new books? If it’s the earlier, it’s borderline criminal. If it’s the latter, I’m unhappy but understand realities.
Some of those customers cannot be upgraded without hardware replacement, we can sell them a brand new system that will do everything (and more) their old one will, but they dont want to spend the money, and we are happy to take the money for support (the old CAPEX vs OPEX argument).
Some of this is sorta easy, its COTS hardware, but we also have much older systems that due to component obsolescence I simply cannot build replacements anymore. 10+ years of support ought to be enough for 90% of the products out there, at some point the answer really is “upgrade your hardware” - we didn’t sign up to indefinitely support not just hardware (much of which we cannot build spares for) much less the software ecosystem around the hardware.
Long term I plan on increasing support renewal costs for systems that are older than 10 years old to encourage hardware refreshes.
Like I still have to have XP VM’s to build firmware for older products, when is it reasonable to cut off service and support?
You can’t equate that to providing ongoing updates and support for a $100 hardware device indefinitely.
They replaced the product, but they kept buying the parts and updating the software for the old one. And customers were absolutely still sending back their broken ones getting at cost replacements.
It was like looking at a well engineered, thoughtfully maintained hole in the bottom of a cruise liner.
For (others) reference the oldest bits of code in our software are from the mid-late 90’s and the oldest systems still paying for support rely on parts to build that is not available at any price, its all just made of unobtainium, whereas I can sell them a brand news that does everything they have today and more.