4 ms·

Then replace the battery and carry on using it?

ChrisMarshallNY 2y ago
May end up doing that. We'll see. I also write software for these beasties, and it may well be that I won't be able to justify avoiding getting one that has Apple Intelligence.
- ryandrake 2y ago
  Eventually, Apple (and 3p developers) will abandon you, and you'll need to throw away a perfectly good phone and take another step on the treadmill. I'm still hanging on to my perfectly working iPhone 7, while app developers tell me to fuck off left and right. It does everything I want a phone to do, but developers consider "old phones" to be icky and stop supporting them.
  - layer8 2y ago
    Eventually yes, but the 13 is less than 3.5 years old and will likely receive iOS updates for another 3.5 years. And most apps support one or two iOS versions into the past. I agree it’s not ideal, but ~8 years of use isn’t that bad either.
  - bschwindHN 2y ago
    Yup - it was the same for me with the 2016 SE. Still runs perfectly fine, we're still doing the same old CRUD web shit for apps, but apparently now our apps are so much more advanced that there's no possible way they could keep supporting that "legacy" hardware. https://blog.bschwind.com/2025/01/11/the-original-iphone-se-is-the-best-iphone-apple-ever-made/ https://blog.bschwind.com/2025/01/11/the-original-iphone-se-...
    - ryandrake 2y ago
      I'm totally with you, with that article. It is terrible how owners of slightly-old hardware are treated by software developers. Leaving potentially millions of users out in the cold because they just can't be bothered to keep a maintenance branch around and backport a few fixes to it. For apps that are by and large not complicated. So much waste sacrificed at the altar of developer comfort!
      - ChrisMarshallNY 2y ago
        My low-end test unit is an old SE (running 15). I'm an iOS native developer. The screen size is the main reason I test with it. However, these days, I usually release with minimum support beginning with iOS 16, because I am a one-man shop. My stuff will usually run in 15, though.
  - raudette 2y ago
    Ultimately, one of the cameras in my iPhone 7 failed, and I replaced it with an SE3 - which was indistinguishable from the 7 - but another issue was patches. With very little skill, I found I could duplicate this issue on my iPhone 7 running the latest supported version of iOS: https://joshua.hu/apple-ios-patched-unpatched-vulnerabilities https://joshua.hu/apple-ios-patched-unpatched-vulnerabilitie...

May end up doing that. We'll see. I also write software for these beasties, and it may well be that I won't be able to justify avoiding getting one that has Apple Intelligence.

ryandrake 2y ago
Eventually, Apple (and 3p developers) will abandon you, and you'll need to throw away a perfectly good phone and take another step on the treadmill. I'm still hanging on to my perfectly working iPhone 7, while app developers tell me to fuck off left and right. It does everything I want a phone to do, but developers consider "old phones" to be icky and stop supporting them.
- layer8 2y ago
  Eventually yes, but the 13 is less than 3.5 years old and will likely receive iOS updates for another 3.5 years. And most apps support one or two iOS versions into the past. I agree it’s not ideal, but ~8 years of use isn’t that bad either.
- bschwindHN 2y ago
  Yup - it was the same for me with the 2016 SE. Still runs perfectly fine, we're still doing the same old CRUD web shit for apps, but apparently now our apps are so much more advanced that there's no possible way they could keep supporting that "legacy" hardware. https://blog.bschwind.com/2025/01/11/the-original-iphone-se-is-the-best-iphone-apple-ever-made/ https://blog.bschwind.com/2025/01/11/the-original-iphone-se-...
  - ryandrake 2y ago
    I'm totally with you, with that article. It is terrible how owners of slightly-old hardware are treated by software developers. Leaving potentially millions of users out in the cold because they just can't be bothered to keep a maintenance branch around and backport a few fixes to it. For apps that are by and large not complicated. So much waste sacrificed at the altar of developer comfort!
    - ChrisMarshallNY 2y ago
      My low-end test unit is an old SE (running 15). I'm an iOS native developer. The screen size is the main reason I test with it. However, these days, I usually release with minimum support beginning with iOS 16, because I am a one-man shop. My stuff will usually run in 15, though.
- raudette 2y ago
  Ultimately, one of the cameras in my iPhone 7 failed, and I replaced it with an SE3 - which was indistinguishable from the 7 - but another issue was patches. With very little skill, I found I could duplicate this issue on my iPhone 7 running the latest supported version of iOS: https://joshua.hu/apple-ios-patched-unpatched-vulnerabilities https://joshua.hu/apple-ios-patched-unpatched-vulnerabilitie...