10 ms·
Everyone here is very positive that the transition will go smoothly based on their last few transitions being fairly successful. I'm a bit more skeptical. Bac
by jedberg 6y ago
Everyone here is very positive that the transition will go smoothly based on their last few transitions being fairly successful.
I'm a bit more skeptical.
Back then, their desktop/laptop business line was much more important to them. They needed it to go well. They were also a niche player and couldn't afford to lose more market share to PCs/Windows.
But now, they barely care about their desktop/laptop revenue (being only 10% of their revenue) and they don't seem to care much about their marketshare either because they don't seem to be doing much to expand it. They care a lot more about their iDevices now.
Also, if the transition from 32 to 64 bit is any indication, they don't care nearly as much about backwards compatibility as they used to. When they did the hardware transitions, they had a compatibility layer (Rosetta) that was supported for 5 years after the transition. But with the 32 bit change, the announced that it would no longer be supported in 2017, and dropped support in 2019, just 2 years later.
I can no longer use a lot of my favorite apps because they were games written years ago with no current support, so they were not updated. Or they're things like the old Microsoft Office, which works perfectly well for me, but I can no longer run. And Apple provided no emulation environment or official way to do so.
So now my choice is to keep an old computer around just to run old apps (which could be a security issue if it's on the network), or buy something like Parallels, which is a ton of overhead for a single app at a time.
It would have been nice if they had provided a Rosetta for the 32/64 conversion. The fact that they didn't does not bode will for this transition.
- robertoandred 6y agoIncluding 64-bit support until Catalina was effectively the same as Rosetta: support for deprecated tech. A Rosetta for 64-bit is just kicking the can.
- jedberg 6y agoRight but my point is they only did that for two years, instead of five.
- yoz-y 6y agoThe writing was on the wall for a decade. And most applications did get an update.
- Wowfunhappy 6y agoThe difference, to me, is that Rosetta was an inherently bad experience for users. The apps ran slower and used more battery, because despite Apple's best efforts, it was still an emulator, and emulators are slow. The amd64 architecture, by contrast, innately supports i386 code—that's a key feature of the platform! Removing support from macOS does not benefit users; it only benefits Apple by lowering Apple's maintenance burden. Given that Apple is one of the richest companies in the world, and they sell Mac hardware at a large markup, I'm not particularly sympathetic to their plight.
- greedo 6y agoThis is ridiculous. Mac revenue was roughly $25 BILLION dollars in 2019. The idea that they don't care about it is simply wrong. Same with the idea that they don't care about marketshare. Of course they care more about iDevices than the Mac. It brings in roughly 5x as much money as the Mac. But Apple can chew gum and walk at the same time.
- jedberg 6y ago25 billion is still only 10% of their revenue. And they won't lose it all by making it a shitty transition. Heck, they won't lose most of it. But if they lose 20% of their revenue because of a bad transition, that's still only 2% of the total company revenue. Why would the spend money on protecting that 2%?
- rrdharan 6y agoIf the money they need to spend is less than that 2%, why WOULDN'T they spend the money?
- jedberg 6y agoThe overhead of hiring people. The overhead of managing an extra team. The overhead of extra QA. The overhead of triaging extra bugs. There are a lot of costs associated with backwards compatibility with very little payoff if it doesn't mean a lot to the bottom line.
- rrdharan 6y agoSure. Note that 2% of $25B is $500M. Companies of all sizes (even FAAMNG) will act to protect that kind of existing revenue. And my point was that you can do all of the things you listed for less than $500M; probably for less than $250M. Developers are more expensive than they used to be but $100M+ still goes a pretty long way.
- renaudg 6y agoBecause the Mac and iDevices revenue streams are not as independent as you imply. Driving the Mac off a cliff would alienate developers and have serious repercussions on the iOS ecosystem as well. Why do you think Apple still builds Pro apps like Logic and FCP ? They are almost certainly losing money given their ridiculously low price point, but they help with brand image and keeping the Mac the go-to platform for creatives. There’s indirect value in that.
- lanna 6y ago> When they did the hardware transitions, they had a compatibility layer (Rosetta) that was supported for 5 years after the transition. But with the 32 bit change, the announced that it would no longer be supported in 2017, and dropped support in 2019, just 2 years later. You are comparing the time a technology was supported with the time it was announced a technology would no longer be supported. 32-bit apps were supported in 64-bit Mac OS systems for at least 7 years.
- jedberg 6y agoFrom what I could find, the first announcement of dropping support for 32 bit apps was in 2017, and the support dropped in 2019. Why would an app maker update their old apps before an announcement was made that they would be deprecated?
- comex 6y ago> Why would an app maker update their old apps before an announcement was made that they would be deprecated? Almost immediately after 64-bit support was added in 2005, it was the recommended path, not only for new apps but for existing ones to migrate to. For example, an document called "64-bit Transition Guide for Cocoa" [1] was first published in 2007. A few years later, another document [2] was more explicit: > Should You Recompile Your Software as a 64-Bit Executable? > As a general rule, in OS X v10.7 and later, the answer is probably yes. OS X 10.7 was released in 2011. Certainly, many – most – app makers did update their old apps. For example, Apple's refusal to support Carbon on 64-bit famously forced Adobe to scramble to update their apps to run on Cocoa, because they considered 64-bit support to be essential. Admittedly, one of the chief benefits of 64-bit was the ability to address more than 4GB of memory, and pro apps needed that more than your average app. But your average app was also easier to recompile, so in practice, pro apps were if anything the slowest to migrate. Even then, most of them did, long before the official deprecation. By the time the deprecation was announced, let alone by the time Catalina was released, most apps that were still 32-bit were the ones that had ceased to receive updates altogether. From that perspective, the exact timing of the deprecation doesn't matter that much: most unmaintained apps aren't going to become maintained again because of an announcement by Apple. It was going to hurt no matter what. [1] https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/Cocoa64BitGuide/RevisionHistory.html#//apple_ref/doc/uid/TP40004247-CH2-SW1 https://developer.apple.com/library/archive/documentation/Co... [2] https://developer.apple.com/library/archive/documentation/Darwin/Conceptual/64bitPorting/indications/indications.html#//apple_ref/doc/uid/TP40001064-CH206-TPXREF101 https://developer.apple.com/library/archive/documentation/Da...
- scarface74 6y agoAlso, if the transition from 32 to 64 bit is any indication, they don't care nearly as much about backwards compatibility as they used to. When they did the hardware transitions, they had a compatibility layer (Rosetta) that was supported for 5 years after the transition. But with the 32 bit change, the announced that it would no longer be supported in 2017, and dropped support in 2019, just 2 years later Apple hasn’t sold at 32 bit only Mac since 2007. To Adobe’s chagrin they didn’t port Carbon to 64 bit with the rest of MacOS in 2007 and they deprecated it in 2012. Were developers really caught off guard that they shouldn’t be writing 32 bit software in 2017?
- slantyyz 6y ago>> Were developers really caught off guard that they shouldn’t be writing 32 bit software in 2017? Probably not, but end users shouldn't have to suffer because they bought software from bad developers. One reason why IE still ships with Windows is because a lot of companies are still using old enterprise software that never got updated for the modern web.
- scarface74 6y agoHave you read Raymond Chen's MS blog about all of the hacks that are in Windows just to keep backwards compatibility with one bad app? Maintaining backwards compatibility forever increases the security vulnerability to footprint, the testing surface for regressions, code size etc. Have you seen how badly Windows runs in low resource environments like the low end Surface line? IE and the collapse of MS's browser market share is not exactly a shining example of how to successfully handle a product.
- xnyan 6y agoYou’re sort of picking the worst example, the alternate is the fact that Windows has maintained a gargantuan desktop OS market share for decades in large part because of their dedication to application compatibility.
- 6y ago
- slantyyz 6y ago>> their last few transitions being fairly successful. Their last transition is specifically what brought me to the Mac after having been away for a decade. I switched to Mac exactly because they were going x86, because I knew I'd be able to virtualize Windows (although it took a year to happen), which was a win-win for me. I'm guessing a lot of people who used Windows at work plus developers on Linux wanting a nice GUI (remember, we're talking mid to late 2000s) were responsible for a lot of Mac growth back then. I have to wonder how many people will switch back if x86 were to get totally abandoned.
- toyg 6y agoI will likely switch back. I'm not an avid gamer but there are a couple of titles I really care about - and I'm pretty sure at least one of them will never make whichever transition Apple will impose, having only barely survived the 32bit massacre. The last few years have really felt like enduring Apple more than enjoying it. It's a shame, because OSX remains great, but there is only so much it can compensate for.
- unicornfinder 6y agoHonestly, I don't think that many will. Back then Mac software support wasn't nearly as good as it is now - I think Apple is in a much better position to drop x86 support.
- slantyyz 6y ago> Back then Mac software support wasn't nearly as good as it is now It might be a chicken and egg thing though. With the influx of people who wanted Macs on x86 and the halo effect of them spreading the word, the app support got much better. Also, because the machines were x86 compatible, I'm sure a lot of enterprise buyers like IBM started to allow their users to get Macs instead of Windows laptops. I obviously have no idea what will happen, but as someone who switched back to Windows a few years ago, I am definitely curious to see how it plays out.
- unicornfinder 6y ago
- goatinaboat 6y agoBut now, they barely care about their desktop/laptop revenue (being only 10% of their revenue) and they don't seem to care much about their marketshare either because they don't seem to be doing much to expand it. They care a lot more about their iDevices now. The selling point of iDevices is that so much content/code works perfectly on them, and that is because it is created on the OSX platform originally. If Apple think they can maintain that experience for customers while developers flock to WSL or Linux they are kidding themselves.
- unicornfinder 6y agoCan confirm a lot of developers seem to be going to WSL lately, including myself.
- nojito 6y ago32/64 isn’t a good analogy because the only reason Apple supported 32 for so long was because Intel missed their deadline for core two duo which led cause the first generation core duos to be 32 only.
- tinus_hn 6y ago> It would have been nice if they had provided a Rosetta for the 32/64 conversion. Until 32 bit support was dropped, the system supported running 32 bit apps and drivers. What kind of ‘Rosetta’ are you looking for?