2 ms·

Playing devil's advocate here with your "short product life" argument but Apple generally release operating system builds for older devices for much longer than

Playing devil's advocate here with your "short product life" argument but Apple generally release operating system builds for older devices for much longer than, say, any Android manufacturer out there does. Why aren't we singling out Samsung or HTC too? For example, iOS 12 still supports the iPhone 5S which was released in 2013 (and actually works perfectly well considering the age of the device, as my work phone can attest). On the Mac front, macOS 10.14 is still wholly supported on computers released in 2012 (and that also works fine, as my 2012 MacBook Pro can also attest). Apple themselves have even acknowledged that the purchasing of new devices has declined significantly recently as people tend to be happier with what they have for longer, knowing that it'll be supported for longer and get feature upgrades for longer. If anything, I would suggest that Apple have never had a harder time trying to persuade people to buy new products.

ksaj 7y ago
I have an old unsupported ipad that I still use to read every night. The planned obsolescence is such that it cannot be charged while powered on - literally doesn't even try. When I power it down, it charges just fine, and the battery is good for another week. Likewise, it harasses the living shit out of me to log in to Apple Store, and since I never do, apps running while being harassed invariably crash on the third attempt at forcing me to log in. To me, this is super unethical. I haven't updated it and never will because of the extent of their trying to needlessly force me into an upgrade that won't improve my experience outside of that harassment.
- colejohnson66 7y ago
  > The planned obsolescence is such that it cannot be charged while powered on Your charging brick isn’t capable of providing enough amps. That’s the problem. Not “planned obsolescence”. Last I checked, the iPad needs at least 10 watts (5V at 2A) to charge. The small 5 watt brick that comes with an iPhone isn’t going to do it.
  - ksaj 7y ago
    I even used a new fast charger and a number of 5V/2A blocks thinking the original one was toast. This only started happening suddenly after an update, and I've never been able to charge it unless shut off ever since. Even the "plugged in" graphic doesn't show, and it will not even try to charge when plugged in to sync. I read about the voltage/amperage thing before, but it doesn't seem to be the case here. It is a sensible solution that I wished would work, but isn't working on mine. Of course, it is possible that the charging circuit inside is worn down or something. But again, it started happening immediately after an update, and no subsequent update fixed it. And now it is unsupported, so it is what it is until it officially croaks.

ksaj 7y ago

I have an old unsupported ipad that I still use to read every night. The planned obsolescence is such that it cannot be charged while powered on - literally doesn't even try. When I power it down, it charges just fine, and the battery is good for another week. Likewise, it harasses the living shit out of me to log in to Apple Store, and since I never do, apps running while being harassed invariably crash on the third attempt at forcing me to log in. To me, this is super unethical. I haven't updated it and never will because of the extent of their trying to needlessly force me into an upgrade that won't improve my experience outside of that harassment.

colejohnson66 7y ago
> The planned obsolescence is such that it cannot be charged while powered on Your charging brick isn’t capable of providing enough amps. That’s the problem. Not “planned obsolescence”. Last I checked, the iPad needs at least 10 watts (5V at 2A) to charge. The small 5 watt brick that comes with an iPhone isn’t going to do it.
- ksaj 7y ago
  I even used a new fast charger and a number of 5V/2A blocks thinking the original one was toast. This only started happening suddenly after an update, and I've never been able to charge it unless shut off ever since. Even the "plugged in" graphic doesn't show, and it will not even try to charge when plugged in to sync. I read about the voltage/amperage thing before, but it doesn't seem to be the case here. It is a sensible solution that I wished would work, but isn't working on mine. Of course, it is possible that the charging circuit inside is worn down or something. But again, it started happening immediately after an update, and no subsequent update fixed it. And now it is unsupported, so it is what it is until it officially croaks.