[highwind]

Just because your drop saw burns out in 10 years that doesn't automatically make my code obsolete in 10 years.

I can make a same counter argument using the same logic. I have a car that runs fine well past 10 year mark. Why can't I expect a software do the same?

[acdha]

Your car didn’t run for 10 years without any maintenance. It’s not unreasonable to expect someone to click build once a decade either.

[alexvoda]

You did not depend on the manufacturer to do that maintenance. The manufacturer could have even gone out of business and you could still fix or find someone to fix your car.

You however depend on the original developer to click that build button because proprietary software. If it was FLOSS, you could.

But don't worry, thanks to DRMed parts you won't be able to fix anything on your car either (or phone, or any other smart device) without the involvement of the original manufacturer. Ain't property wonderful when the manufacturers intelectual property has precedence over your physical property?

/s

[acdha]

I think you misunderstood the analogy - the app is the car, not the parts. Once you correct that it’s easy to understand why the rest of your message doesn’t make sense.

[antihero]

Not running on modern architecture does make it obsolete in the same way that stuff that’s only available on punch card is obsolete.

Why is it up to others to spend resources supporting backwards compatibility instead of you to keep your code compiled for modern arch?