13 ms·
The Ars Technica article on this issue cuts to the heart of why this is so devastating: there is tons of software--software which was really interesting and I d
by saurik 10y ago
The Ars Technica article on this issue cuts to the heart of why this is so devastating: there is tons of software--software which was really interesting and I dare say "seminal" for this important era of computing; and which is not old or outdated by any sane standard--that this destroys access to going forward, for essentially no benefit.
Apple insisted that they get to curate something of critical value, but they don't comprehend the moral weight of that responsibility, and now want to just go around burning down their Apple-branded libraries. It is absolutely sickening, and is the kind of thing we probably need to solve using regulation (which, of course, is likely never going to happen, given how even companies we would have assumed were on our side often have lobbyists fighting for the ability to lock down ecosystems).
https://arstechnica.com/apple/2017/01/future-ios-release-will-soon-end-support-for-unmaintained-32-bit-apps/ https://arstechnica.com/apple/2017/01/future-ios-release-wil...
- Athas 10y agoSaid software can still be run using emulators, can it not? There is lots of (well, some) potentially useful software out there that only runs on machines no longer in production. A good solution is also to make source code freely available, then the best programs will not die.
- saurik 10y agoI happen to know someone who had managed to build an emulator for iOS, but it could only emulate one particular old device (the key thing to understand is that we had a bootrom exploit that let us dump a lot of the code and encryption keys from these older devices). The issue with Apple goes well beyond distribution of apps: they also control the hardware, and they use that control to shroud the software; and unlike with a typical game console, there is a ton of software running on the device as part of a network of dependencies. But like, we can go further: as it stands, without exploits for security vulnerabilities for these devices, it isn't even possible to get a copy of the apps to run in an emulator, due to the as-yet uncracked DRM used by Apple (which may or may not use hardware AES keys; I still haven't figured this out). So even if you had an iPhone emulator (and you don't, and might not for a very long time, if ever), you also need to obtain an unencrypted copy of Trainyard (the app in the banner image of this article) to run on it, as if they really are using hardware AES keys for that, your emulator is going to be missing those. Essentially, I would argue that we are moving into a post-emulator reality. It was really easy to write a Nintendo emulator, and it was sort of OK to write a Nintendo 64 emulator. The existence of Wii and PS3 emulators is only due to bugs in security of systems, often the kind that are caused by people too often using unsafe languages like C. Imagine a world where people with intent to lock things down and the experience to know how to do it well are also coding in secure-by-default languages: you get to a point where even a scanning tunneling microscope isn't enough to get you access to the code either from the console or from the game.
- userbinator 10y agoImagine a world where people with intent to lock things down and the experience to know how to do it well are also coding in secure-by-default languages: you get to a point where even a scanning tunneling microscope isn't enough to get you access to the code either from the console or from the game. This is why I've always found these "safe" languages and the general security trend rather worrisome: they can effectively secure our devices against attackers, but also against their owners. Personally I think these issues need to be solved before advocating for these more secure systems, as otherwise we'll just be locking ourselves out.
- majewsky 10y agoSo... we have to wait for quantum computers to break the AES keys? :)
- foobiekr 10y agoQuantum computers are only marginally faster against symmetric key encryption - AES128 requires 2^64 quantum operations.
- sjtgraham 10y agoI've been looking at the FairPlay DRM this week. I followed the path from the memory pager, through IOTextCrypter et al, through to fairplayd via com.apple.unfreed IPC. Static analysis of that binary looks impracticable (a lot of effort appears to have been made to ensure this), but have you considered dynamic analysis using Unicorn?
- quotemstr 10y ago> moving into a post-emulator reality Also known as the death of the general purpose computer. Free software advocates have been warning about this slow-rolling catastrophe for ages. http://boingboing.net/2012/01/10/lockdown.html http://boingboing.net/2012/01/10/lockdown.html
- xj9 10y agoi'd just like to interject for a moment.. i wonder how long it is going to take for people to realize the importance of libre software. sure, strong copyleft can be inconvenient for developers, but that inconvenience must be borne to enable users to control their technology. otherwise we end up with the nonsense that we are discussing here: software people want/need, that they are no longer permitted to use because Apple said so. https://www.fsf.org/ https://www.fsf.org/
- jl6 10y agoQuite. When you accept a dependency on proprietary software, you open yourself to the risk of the vendor withdrawing support. Looks like that risk materialized for some users today. This is an "I told you so" moment for a lot of Free software advocates.
- saurik 10y agoFWIW, as a serious advocate of Free Software (someone who constantly travels around to developer conferences, college hackathons, and even sci-fi conventions giving talks that stress the benefits of the GPL3), this doesn't help and almost becomes a non-sequitor, as it makes it sound like a business decision related to productivity applications. I doubt anyone would say they "rely" on Trainyard, and the Trainyard developer did "rely" on iOS, but they probably liked that and for all I know they are dead now (I realize they almost certainly aren't, but like: this is the extent to which they aren't relevant). As a free software advocate, there isn't a group of "some users" whom I get to point at and say "I told you so": in fact, most of the people who played Trainyard and enjoyed it probably don't even care that it is going to be inaccessible. And while I sort of care myself about some specific applications, it isn't about people like me either. The devastating reality is that this purge of 32-bit software combined with the centralized control on the computers that are capable of running it is a devastating blow to society as a whole, and the people who are causing it are the people who either don't directly feel the downsides (as historical preservation is an externality, like pollution) or are actually in the minority of people who experience an upside. Advocating for free software is good as it can be a weapon in this fight, but in practice Apple just isn't feeling the burn: when they wanted a new compiler, they hired a ton of engineers and wrote one so they didn't have to rely on gcc anymore. There is only so much power in the lever of free software to force societal change in a way that doesn't continually lead to a handful of resistance fighters looking at the carnage of the land and thinking "I know what will make me feel better: I'll point at the majority of people who don't even understand this enough to notice and the handful of people who are happy this happened and yell 'I told you so'", particularly when developers like Linus Torvalds, who have critically important positions, aren't fighting for the same battle. My claim: we need regulation. In the same sense that we have regulation about pollution--to keep a handful of people who benefit from pollution enough to not care about its downsides to society (and them) from doing horrible things--we need to regulate companies like Apple to force them to provide open platforms and to have some reasonable set of responsibilities when it comes to sunsetting older hardware. The issue of closed vs. open ecosystems is related to free software, but isn't the same, and we need to be paying a lot more attention to the former and avoid a lot of knee jerk to the latter if we want to prevent some of the worst case scenarios.
- cpeterso 10y agoHow can a user tell whether an iOS app is 64-bit? I use some old apps that are no longer maintained and worry that they will just stop working.
- saurik 10y agoIf you are on iOS 10.1 or later, you should get a dialog box that clail the application "may slow down your phone" (this dialog'a appearance is remembered and only shows up occasionally per app, I believe). http://www.macrumors.com/2016/10/06/ios-10-1-32-bit-app-alert/ http://www.macrumors.com/2016/10/06/ios-10-1-32-bit-app-aler...
- masklinn 10y agoAh so that's what that warning is about.
- freehunter 10y agoIs there any way to tell before you buy an app? I just bought one yesterday, actually paid money for it, and it gave me that warning. While six months is a long time, if I buy it the day before the cutoff, I'd be pretty disappointed when I lose access 24 hours later. I also wish there was a way to see which apps support retina displays before you buy them, I've been tricked a few times.
- ValentineC 10y ago> Is there any way to tell before you buy an app? I believe that most apps built to support "iOS 8 or later" (this is shown in the app's Information section) are 64-bit. > While six months is a long time, if I buy it the day before the cutoff, I'd be pretty disappointed when I lose access 24 hours later. I just looked it up, and Apple has been asking developers to build against the iOS 8 SDK for 2 years now: http://appleinsider.com/articles/15/01/19/apple-once-again-alerts-ios-8-app-developers-to-upcoming-64-bit-requirement- http://appleinsider.com/articles/15/01/19/apple-once-again-a...
- valuearb 10y ago
- jmgao 10y ago> The Ars Technica article on this issue cuts to the heart of why this is so devastating: there is tons of software--software which was really interesting and I dare say "seminal" for this important era of computing; and which is not old or outdated by any sane standard--that this destroys access to going forward, for essentially no benefit. It's not zero benefit. Supporting multiple ABIs means that you need to have multiple copies of system libraries paged in at a time if they're used, which is not an insignificant amount of memory (which then has resulting power/price costs). It's possibly even bigger of a problem on iOS than Android, because Apple changed the floating point ABI between ARMv6 and ARMv7, so they have to support multiple different 32-bit ABIs.
- saurik 10y agoThat only matters if you are using 32-bit software. Deleting the 32-bit software is not somehow a benefit with relation to that goal. You are saying that it is better to run all 64-bit software. I am arguing that there is essentially no benefit to a device that is incapable of running 32-bit software when it clearly still has the hardware.
- npunt 10y agoI think you're assuming the upcoming A11 chip will also be capable of running 32-bit software. The hardware may be changed, for the sake of simplicity.
- saurik 10y agoAs far as anyone is reporting, Apple is intending to remove support for existing devices that get updated to new versions of the firmware, not just for new hardware.
- crottypeter 10y agoLack of fragmentation is a good thing. As others have said important software will be made available. Apple has the luxury of a dedicated userbase and can afford to make these calls.
- Reason077 10y agoIt is ... the kind of thing we probably need to solve using regulation Apple already have a technical solution: bitcode. In the future, this should mean the App Store can automatically recompile old binaries for new CPU architectures.
- koko775 10y agoNo. It is not that abstract or general. It enables tuning, but several aspects of the target architecture are assumed in the bitcode. It allows for CPU-aware optimization passes, such as - for example - reconfiguring math to use faster instructions when possible, but it is specifically not an abstract machine-independent bytecode.
- Reason077 10y agoTrue, bitcode is not completely abstract, and things like calling conventions are baked into the bitcode. But it is abstract enough that Apple could use it to recompile binaries for, say, a new 64-bit CPU architecture. Yes, they might have to jump through a few hoops to make it work, but given the control that Apple have over their platforms (they can define things like calling conventions) it shouldn't be too difficult. Apple did JIT compilation of binaries during the PowerPC -> Intel transition years ago. Recompiling bitcode on the App Store would be easy by comparison!
- nstj 10y agoLattner refuted the ability of Apple to recompile bitcode into alternate architectures in his recent ATP interview
- Reason077 10y agoLattner said that bitcode is "not a panacea that makes everything magically portable"[1], which of course is true. But that doesn't mean it couldn't be recompiled for different architectures, given reasonable bounds like both 64-bit, same endian, similar calling conventions, etc. I'm not suggesting Apple is considering that, just that it would be technically possible if there were ever a compelling reason. It's unlikely they would ever move away from ARM on iOS, but on something like the Apple Watch with it's highly custom SIP, and ultra-low-power requirements, you never know... [1] http://atp.fm/205-chris-lattner-interview-transcript/#bitcode http://atp.fm/205-chris-lattner-interview-transcript/#bitcod...
- nstj 10y agoAnyone have any examples of a "seminal" iOS app which is still 32 bit?
- givinguflac 10y agoNo, no they don't. Any app that's still 32 but hasn't been updated in almost two years. How crucial could it be?
- PinguTS 10y agoHow about an App that controls stuff where the iPad (or iPod) is just used as a "cheap" HMI. For example iPads are used in stage control with dedicated Apps. The hardware, which the App controls, does not change. But the iPad itself has to be replaced with a newer one, or even you can't buy old ones. Think about, building control which is build for 20+ years.
- Jtsummers 10y agoIf you're using it in that situation and you're blindly updating the OS, you're doing it wrong. You have a very explicit dependency, the application. The OS shouldn't get touched unless you know the application is supported by it. We have, similar, setups at work for our test stations, though with Windows holding the interface application. Essentially replacing walls of control panels with one application and computer. We do not push OS or major library updates to those computers until we have verified that the application will either be unaffected or has been updated to correct whatever issues the new OS or library introduce.
- ordbajsare 10y ago"solve using regulation" Nothing solves problems the using the violence of the state.
- numbsafari 10y agoThink of all the web sites optimized for IE6. If those apps are so seminal, let's hope they are open source and available for study, porting, and upgrading.
- danbee 10y agoThose websites should still work perfectly well on modern browsers (unless they use ActiveX components of course).
- digi_owl 10y agoDid we read the same article? I am looking a whole lot of Cunningham worlds for how this move by Apple is a good thing...
- interpol_p 10y agoWhy do you and many others treat software as if it is a sacred artefact that must be kept and preserved and be able to be run for all future generations? Humans are producing so much content right now in the form of software, art, movies, writing. Does it really matter if we leave some behind? Do we need to preserve every piece of information we generate? I have software on the App Store that I cherish that unfortunately will never be updated past 32 bit (too much work). But I don't care, nor do I feel the need to preserve it. You say there is no benefit to this move. But this move significantly reduces Apple's technical debt and support requirements and is likely to be worth the tradeoff for future developers and future software on the platform.
- wolfgke 10y ago> Humans are producing so much content right now in the form of software, art, movies, writing. Does it really matter if we leave some behind? Do we need to preserve every piece of information we generate? Everybody should be able to decide for themself what they consider as important and what should be preserved. So I strongly oppose when the benevolent/malevolent dictator decides that you have to leave this piece behind. > I have software on the App Store that I cherish that unfortunately will never be updated past 32 bit (too much work). But I don't care, nor do I feel the need to preserve it. But others perhaps care. So I strongly encourage you to open-source it if you don't care about it anymore.
- mulletbum 10y agoNo they shouldn't. Those people should either update their software or force their users to stay on legacy devices. It should not be Apple's responsibility to not move forward and continue to complicate their environment for the benefit of the few.
- interpol_p 10y ago> So I strongly oppose when the benevolent/malevolent dictator decides that you have to leave this piece behind. There is no one dictating that. The source code is still in the hands of developers, and your advice to me was to "open source it." All developers of 32 bit apps have that option, and they also have the option to maintain their source going forward. Apple's decision to shed technical debt shouldn't be seen as them eschewing some moral responsibility to support old software. > But others perhaps care. So I strongly encourage you to open-source it if you don't care about it anymore. I would consider it if I still had the source. But you should realise that saying "open source it" trivialises the amount of effort and emotion required to do so. Sharing your work with the world (especially if you are embarrassed by old code you have written) is not something that everyone finds easy to do. I would feel obligated to update the code, write build instructions and a readme file at the very least. That would take a good few days of my time to make the code "presentable" before I would be willing to share it. I don't have the mental or emotional energy to devote to that task.
- andrewmcwatters 10y ago> is the kind of thing we probably need to solve using regulation No, no, no, no, no. This is absurd. Government has absolutely nothing to do with this. This kind of "regulate everything that exists" is why we have some of the problems we do today. You can't go up to someone or some organization and force them by gunpoint to do something like this by law.
- mtgx 10y agoI'm okay with Apple switching to 64-bit only. I wish Google did that a while ago, too. Now, the vast majority of low-end phones use Cortex-A53 (64-bit) chips anyway. However, it's frustrating to see them prioritizing this move over the HTTPS-only one, which they've recently delayed. I'd much rather they push that through, whether developers like it or not, than this. https://9to5mac.com/2016/12/21/apple-delays-requirement-for-https/ https://9to5mac.com/2016/12/21/apple-delays-requirement-for-...
- scott_s 10y agoI suppose I also don't comprehend the moral weight of the responsibility for running 32-bit code. What sort of problems do you foresee happening?
- runjake 10y agoSuch is progress. And there is plenty of benefit: a cleaner, saner iOS, and software that's been updated can take advantage of the latest Apple technology. Perhaps it would be more worthwhile to identify the apps/frameworks you value and bug their authors to modernize them to meet current technological standards. It's not like Apple is springing this one people. They're giving them ~18 months of warning.
- unethical_ban 10y agoThis is the price of using Apple and Google gardens. Would you like reasonable freedom? Build a web app. I would be very hesitant to legislate Apple supporting 32bit apps. That sounds absurd on its face.
- scarface74 10y agoHow is this different from console manufacturers not making their software backwards compatible? If you want to preserve old iOS software that you bought, do a local iTunes backup and your apps are on your hard drive. For the forseable future, you will be able to buy used 32 bit iOS devices - just as people buy used consoles to play old games. That's the worse case, best case is that Apple keeps allowing older devices to run older versions of purchased software. I recently charged up my 1st gen iPad (last update 5 OS versions ago) and I was able to download older versions of apps - Hulu, Netflix, Crackle, Plex, Amazon Video, kindle, Spotify and Google Drive, -- from the App Store. The iPad 1 is too old and too low on memory (256Mb) to run Safari without crashing constantly, but the apps I mentioned still run well as does the built in mail and calendar apps. It works with Bluetooth and Spotify doesn't force you to listen in shuffle mode on tablets if you're not a subscriber.
- kakarot 10y agoSoftware enthusiasts and power-users will still find a way, whether with unlocking, modding, or emulation. Communities will surely spring up that cater to those looking for old iOS / Android software and sandboxing tools will allow these to be safely run. Do not fret :)