I've mentioned this in another comment but: this update will permanently disable any 32 bit iOS apps you have on your device with no recourse or downgrade possible.
So, reason not to update: you like using software you've paid for.
So, reason not to update: you like using software you've paid for.
Anyway I’m sharing this because the “my ancient unsupported 32 bit applications will fail”, while a minimally valid reason not to upgrade, reminds me a bit of the sob stories people would tell to get tech support for their stolen iPhones…
You're being unfairly harsh here. Most likely they bought it off the second hand market because in many countries people can't afford the prices of new iPhones, and then realized it's a stolen phone.
Just like it's the buyers responsibility to make sure they aren't purchasing a stolen vehicle, it should be equally the buyers responsibility to ensure they are not purchasing a stolen phone. Proof of a clean IMEI would be a start. The problem stems from most countries outside the US not taking the IMEI database seriously and so in some countries it's possible to activate a phone with a reported stolen IMEI.
I personally think Apple's choice to restrict activating stolen iPhones is a smart move overall. If countries won't use the IMEI database, this is the next best thing. It's not our responsibility to "unlock" phones for people because they didn't perform due diligence.
Then it your responsibility to have backups no? Forget theft, if you keep all your most valuable data on just your phone alone, you're one accident away from loosing it al, via so many ways other than theft.
>Just like it's the buyers responsibility to make sure they aren't purchasing a stolen vehicle, it should be equally the buyers responsibility to ensure they are not purchasing a stolen phone
Now you're moving the goalposts. A phone is not a car. If my car is stolen, I can't just walk into a Ford-Store and buy a new one on the spot for $1000.
What about stolen bikes? Police don't bother investigating such things and they'll basically laugh you out of the police station.
Yes, so do I and everyone else, but that's why most people pay for cloud backup services (iCloud, etc) or set up their own if they're tech savvy enough. So when they break their phone, their data is still safe.
Still, this has nothing to do with theft. You can easily drop your phone on the ground or have it fall in the ocean on vacation. If your phone is such a valuable tool to you that you can't live without then it's up to you to get various insurance policies (phone insurance, a backup phone, etc.)
And you could physically connect mass storage to an iPhone since before the iPhone (iPod days, same connector, same adapter) but unless it was jailbroken you could do almost nothing with it
Fortunately, unless you're doing hacky bullshit, changing from 32 to 64 bit should be trivial. Unfortunately, companies go out of business, so can't be relied on to update their own software into perpetuity. Fortunately, it probably doesn't have to the original company to update the software, because it should be a straightforward update of some build parameters. Unfortunately, proprietary, source-unavailable code is the norm in commercial software development, so no one but the original company has the source code. Thus it's the original company's fault for not being at least source-available.
Fortunately, we have the technology to run 32 bit software on 64 bit operating systems. Unfortunately Apple has decided to not do so any more. Fortunately, Apple used to allow this, so your software still works on an older version of the operating system. Unfortunately, Apple has decided to brick that version of the operating system, forcing you to update it and lose access to the software you were perfectly capable of running on your device before Apple's unilateral decision. Thus, it's Apple's fault, for breaking backward compatibility and then forcing people to update.
Sure tools etc can last a lifetime , but my drop saws motor will probably burn out in 10 years and will be replaced with an upgraded model ?
This might not be apparent to engineers who see everything as a formula waiting to be solved from first principles.
However, some things move pretty quick and warrant updates to the whole document especially when the document is used a handbook in critical situations. The ACLS protocol manual, updated quinquennially, comes to mind.
Some textbook publishers are intentionally making small changes from year to year to intentionally make the life of those using second hand text books miserable.
Corporations have long since realised that often their biggest competition comes from their own products therefore we now have planned obsolescence (someone who already has your product and doesn't want to buy another) and the war on secondary markets (someone other than you selling your, old, product).
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?
Why is it up to others to spend resources supporting backwards compatibility instead of you to keep your code compiled for modern arch?
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
Software's even better! Since it was inherently digital to begin with, I'm able to make leaps like that with ZERO data loss! The only thing that kills software permanently is planned obsolesce. It doesn't matter what the lifetime of your saw is, that's like arguing that you should be free to shoot nonagenarians because most people don't live that long anyway. It's not about how long other stuff lasts, it's about the fact that it was perfectly capable of going on living until it was killed.