Even a manufacturer of physical goods can decide to stop providing you with spare parts (or, what is common too, to make it more and more expensive so that a repair is no longer worth it). Or a company who manufacture or sold that physical good to you could decide to not support it anymore.
Tend to have non-oem repair parts and I've already mentioned what happens when repair is more expensive then just upgrading. The thing is, in both scenarios, the option of repair is still there.
Also, OEMs tend not to stop producing parts etc within a decade of the goods manufacture. The only exception may be if the good was a dud in the market, but not usual.
So you would be ok with paying $600 for a fridge repair, but not ok with paying $600 for a software update what not only fixes your problem, but upgrades you to a new, current "fridge"?
What is the repair cost versus the replace/upgrade of each individual item? $600 for one doesn't necessarily have the same value as $600 for the other.
For instance, the $15k software I mentioned. Upgrade for X-1 is $1k, X-2 is $2k, X-3 $3k, beyond that, full price. Dongle replacement is $300, but that's only available til the next version hits (when the software I have becomes X-1).
Agree. But you want SAi to upgrade a licence server for outdated software (the successor of Flexi 8.5 is on the market since 2010) at own costs to help customers not to pay for an upgrade. Recognize the contradiction.
Not necessarily have to upgrade the server. Provide a means of DRM that doesn't require going through a server (we are talking about the ability to get a dongle for the software). Or, they can do what Adobe did with CS2. After this is legacy software, not going to be sold through them anymore. Make a little extra money by selling that at a discounted price, keep in good thoughts with that customer then when they have to upgrade (either having too modern of an OS or purchases equipment that requires newer drivers), SAi doesn't bring a bad taste in their mouth.
No matter what someone is going to have to upgrade at some point. They are going to be at such a new OS that it isn't going to install on, or to get it to install on, have to jump through hoops to make it work. I had another software package that was compiled for XP, once 8.1 hit, in order to install, I had to manually move DLL files (only reason I know to do that and where to put them was a popup during install). How many average computer users going to do that? At that point, they are going to upgrade. Here, they may have to upgrade to a newer machine that requires a newer method.
Even my favorite method of running legacy software that requires legacy OSs, VMing. Still run the risk at some point of the guest OS support being deprecated and removed in the VM software. Emulation may be the only way to handle it then, but the ubber performance hit on that method really makes the C/B of that out of whack to the C part.
Also bare in mind you said this before:
When buying a car, a printer or cutter, a stove or fridge for the kitchen, a TV or any other hardware, we all know that the time will come that it breaks down and needs repair or replacement ... but we don‘t want to accept that with software?
This applies to the very server that SAi uses for activating licenses. Expecting them to budget and/or plan for an alternative means should not be out of the question. They chose that method of DRM for a
perpetual licensed good, they should have done a thorough C/B of it to make sure that's the way they should have gone.
What happens if they had an issue with their server at a much earlier time period?