|
|
|
|
|
by scarface_74
1084 days ago
|
|
What’s “unclear”? A modern web browser wouldn’t be any more performant than a safari is in 2023 on any pre-64 bit iOS device. Not that 32-bit or 64-bit by itself makes a difference. But the devices were dreadfully slow and RAM constrained by todays standards. Which modern browser engine do you real think would work decently on such a device? Besides that, no pre- 2012 iOS devices supported 4G and the carriers are dropping 3G support completely in the US by the end of the year. Apple hasn’t abandoned any 64 bit post 2013 device yet. It reduced a security update for the iPhone 5s this year. |
|
Yeh. That's why people turn them into DNLA servers or FTP heads or motion sensors or security cameras or weather machines, spotifyd servers, Docker playgrounds, RC cars, GPIO controllers, home assistants, esoteric K8s nodes, et. al.. There's plenty of things you can do with hardware you don't intend to directly interact with, things that the iPhone is perfectly suited to do.
> Which modern browser engine do you real think would work decently on such a device?
Webkit? You can still build it for 32-bit arches, I don't really see what the holdup is. Firefox could squeeze into ~100mb of memory if you're light on tabs, and Chrome would... well, run. With a little help from swap space.
> Besides that, no pre- 2012 iOS devices supported 4G and the carriers are dropping 3G support completely in the US by the end of the year.
That's fine. If you want to use iOS, use iOS. Running the entire iOS userland would be a complete waste of CPU cycles if you wanted to just use it as a homelab.