8 ms·
OS X at its core, is just Mach + FreeBSD. People were running Darwin in limited resource environments for years. By the time the iPhone hit the market, there w
by heavyset_go 5y ago
OS X at its core, is just Mach + FreeBSD. People were running Darwin in limited resource environments for years.
By the time the iPhone hit the market, there were already plenty of handheld devices that had similar specs that were running full-blown Linux.
Pretending that the iPhone was "at the edge of what was technologically possible" is rewriting history.
- unfocussed_mike 5y agoIt was at the edge in a few small ways but it was carefully profiled to be that; it had limitations (single process model) that didn't really matter (except the absence of 3G) in favour of performance (graphics, capacitive multitouch) that did. It was out in front in a lot of ways but not witchcraft.
- cpuguy83 5y agoThat's just it, craft. They took the time to craft the system to fit a certain profile which people found desirable and it changed the industry.
- unfocussed_mike 5y agoRight. The common criticisms about Apple kit, at any point in time, will be led by feature comparison rather than benefit comparison. On almost every level, the iPhone prioritised benefits (consistency, simplicity, responsiveness, discoverability) over features. And in all but really two of the feature cases (text management/copy and paste, and the absence of 3G), they gambled right: people cared about the benefits they'd engineered for, and not about the features they'd skipped. (They managed to bluff past the apps question: we knew they had to be working on it and they managed to tell us they were working on it without telling us they were working on it) Commentators still make this mistake with Apple.
- imwillofficial 5y ago“It was out in front in a lot of ways but not witchcraft.” I’ve been running Linux since 14. Had all the great smartphones of the age. At 19 I purchased the first iPhone. It was fucking witchcraft.
- unfocussed_mike 5y ago> I’ve been running Linux since 14. Judging by the maths I was running it when you were four or five and have done ever since. I'm not sure what point you're making. > Had all the great smartphones of the age. Good for you. So you ran the handhelds.org linux project on a Compaq iPaq back in 2002-2003, or no? > It was fucking witchcraft. It was not. Apart from the multi-touch implementation which is transformational. Apple did not put anything in that device that other manufacturers didn't have access to, and their device lacked capabilities others had. They just did it right.
- imwillofficial 5y agoNope, I contend chicken blood must have been spilled in pentagram marked areas because after using the first iPhone I was spellbound.
- mushyhammer 5y agoShow me the handheld devices that were running full-blown Linux at the levels the iPhone was (i.e. with a responsive UI). Linux being Linux I’m sure it can be run on a sock but that’s not the same as what iPhone OS 1.0 was.
- unfocussed_mike 5y agoWell of course they weren't running it at iPhone level performance. First because the device and the software hadn't been optimised for each other. And second, the fact that iPhone OS was not a "full blown" Unix OS is precisely why it _did_ have that performance on otherwise reasonably similar Samsung ARM hardware (better specs but not, you know, alien technological advance stuff). The point is that there is this tradeoff. Developers who'd squeezed full multitasking Linux into phones would have been well aware of the kind of performance they'd see without multitasking and without a BSD subsystem. FWIW Jim Gettys' handhelds.org project was demonstrating -- years earlier -- pretty impressive Linux GUI performance on much earlier hardware that had been only modestly adjusted for it [0]. Including for example tilt-sensitivity. Those who knew about those projects could see that Apple had likely benefited enormously from seeing what was being done, and had decided to make an OS profile for iPhone that prioritised single-app performance with a sizeable slice of OS X. [0] The iPaq as a product was designed in part to explicitly accommodate research from the DEC Itsy on off-the-shelf devices
- heavyset_go 5y ago> Well of course they weren't running it at iPhone level performance. First because the device and the software hadn't been optimised for each other. I disagree entirely. Maemo as designed, built and optimized for low-powered mobile devices compared to desktops.
- wmf 5y agoIf it was so optimized, why did it let apps run down the battery in 30 minutes?
- tambourine_man 5y agoOS X is not Darwin. All the interesting parts are on the layers built on top of it. What was remarkable was being able to run a graphic accelerated version of AppKit built for touch screens (UIKit) and have RAM to spare to run a non trivial app, like, you know, a full blown web browser, all in 128MB. So yeah, Darwin + window server + springboard + Safari + webpage > 128MB is pretty impressive indeed.
- heavyset_go 5y ago> OS X is not Darwin. iOS is not OS X. > So yeah, Darwin + window server + springboard + Safari + webpage > 128MB is pretty impressive indeed. Maemo did all all of this years before, and in 64MB of RAM.
- tambourine_man 5y agoI don’t think Debian wasn’t doing double buffering GPU compositing of the UI. Nor was it running WebKit. Show me a video of a smooth pinch to zoom on a webpage with MicroB
- heavyset_go 5y agoKonqueror has modular backend support, and it shipped with WebKit support as backend before the iPhone was released. Rekonq also used it and not KHTML. Epiphany used WebKit since mid-2007, it's now Gnome Web. All were available on Debian and Debian-based distributions. Phone-wise, Symbian used WebKit in 2005.
- wvenable 5y ago128MB is absolutely massive compared to the hardware that NextSTEP / OS X was designed to run on. https://en.wikipedia.org/wiki/NeXTstation https://en.wikipedia.org/wiki/NeXTstation
- tambourine_man 5y agoNextSTEP didn’t run Safari, nor Quartz or Aqua. And NextSTEP was slooooowww. One of the reasons some of us rooted for BeOS.
- cpuguy83 5y agoI think you are mis-remembering history. People were in awe of how responsive the system was. Things like the pins dropping on the google maps app seemed faked, bo way they could do it.
- pinephoneguy 5y agoI had a Zarus at the time. It could run X11 and java apps and even had a self hosting dev environment. The iPhone was mostly a regression from that.
- deleted 5y ago[deleted]
- imwillofficial 5y agoWhat everyone wants, X11 and dev environments on their cell phones. You sir, are a visionary.
- pinephoneguy 5y agoPeople don't like the constraints of smartphones but they don't understand computers well enough to articulate it. That you do and then you mock me for pointing it out indicates a particularly ugly kind of follower mentality. X11 isn't that important, it's the large app library it brings with it (many apps that after 24 years still have no replacements on either smartphone OS.) For power users the flexibility is nice too. Onboard dev environments aren't useful to most people but it indicates/allows a few things: 1) Individual users who are inclined can easily improve the platform with very little effort. 2) The owners of the platform aren't stopping people from doing what they want with their own devices.
- imwillofficial 5y agoWrong, people love the constraints. Or else smart phones wouldn’t be the most popular computing devices in history, and we’d all be rocking mobile terminals.
- pinephoneguy 5y ago>Popularity -> utility Talk about tired arguments. All popularity really means is good PR. As to toasters and Nintendos, yes I do whatever I want with those, toasters have nothing to stop me and Nintendos are usually trivial (and often have flash carts available) to get a shell on.