I can't. I can run the latest versions of Visual Studio and Android Studio on Sandy Bridge (2011) machines running Windows 10. Tying Xcode to the operating system version is either very, very lazy or a means to push developers to not hold on to machines for too long (probably a mix of both).I can see an argument for requiring XCode to be on the latest OS. As for everything else, I usually stay a major version behind on my Macs and I've never had a problem. I wouldn't call that "aggressive about requiring the latest OS."
Personally I deliberately was a buyer of the top end intel 2020 air because I wasnt sure how smooth the rollout of the ARM machines would be, while it was super smooth I have no regrets about my decision, it served me well and I picked up an M4 air earlier this year in anticipation of them dropping more intel support this year.I feel for you if you were one of the last Intel MacBook Air buyers in 2020 right before the M1 came out, but 5 years of feature updates and still another 2 to go of security patches isn't that bad. There's also OpenCore Legacy Patcher that will very likely allow you to run macOS 26 just fine (and future versions too as long as they still have x86 architecture support)
Apple is very aggressive about requiring the latest OS.
For example, XCode requires 15.2 or later.. which came out in December.
If the developers are forced to use the latest OS, how well do you think they'll support older ones for their apps?For the (warning pulled from ass statistic ahead) 99% of Mac users that dont install Xcode that isn’t an issue. Xcode is targeted at people developing for the Apple ecosystem, so this isn’t that weird.
I wouldnt count it as experimental on M1s or M2s, it’s basically just missing thunderbolt support at this point. I have an M1 mini running Asahi as my primary workstation in my garage workshop and it’s rock solidAsahi won't even boot on M3 or M4 Macs. It's experimental and suggesting anything but is a disservice.
Interestingly, I'm not sure it needs to be; Apple developed it in-house didn't they? The reason for pulling Rosetta was that the tech was licensed from Transitive: https://meincmagazine.com/uncategorized/2005/08/5195-2/ - since Apple owns the entire stack here, the only reason for pulling Rosetta2 is to simplify the stack and testing. Considering for Microsoft, the Intel translation layer in Windows ARM is still a major selling point, I can imagine Apple keeping it around for a while. If they don't, then they effectively lose the part of their market that is trying to build/test/run Intel-related stuff, which is MUCH more entrenched than PPC was 20 years ago.When will Rosetta2 be pulled? (The X86 translation layer for Apple Silicon Macs).
15.2 supports machines as far back as 2017, so I'm not really seeing that as a big issue. But again, the larger point is that a machine that's not supported by MacOS 26 works just as well at this moment (and for quite a while in the future) as it did before the keynote. It's not suddenly more vulnerable; the software on it hasn't magically stopped working. It's just a workable as it was a few hours ago.Apple is very aggressive about requiring the latest OS.
For example, XCode requires 15.2 or later.. which came out in December.
...it's twelve years old, man.I have a 2013 Retina MacBook Pro that unfortunately has such an old i5 that can’t be upgraded to Windows 11, so even Bootcamp isn’t an option for me once October rolls around unless I go Linux.
If developers aren't using the latest OS, how well do you think they'll support newer features and architecture?If the developers are forced to use the latest OS, how well do you think they'll support older ones for their apps?
So cool that the MacBook Air I bought my wife less than 5 years ago is no longer supported.
Yes, good answer. Apple's game porting toolkit uses Rosetta2 AFAIK.Interestingly, I'm not sure it needs to be; Apple developed it in-house didn't they? The reason for pulling Rosetta was that the tech was licensed from Transitive: https://meincmagazine.com/uncategorized/2005/08/5195-2/ - since Apple owns the entire stack here, the only reason for pulling Rosetta2 is to simplify the stack and testing. Considering for Microsoft, the Intel translation layer in Windows ARM is still a major selling point, I can imagine Apple keeping it around for a while. If they don't, then they effectively lose the part of their market that is trying to build/test/run Intel-related stuff, which is MUCH more entrenched than PPC was 20 years ago.
If the OS does not support intel, which macOS27, let alone '28 will not, there will be no OCLP for it...You can always use for, two years more? OpenCore to update to macOS 2028
just like how XPostFacto ended when PowerPC builds endedIf the OS does not support intel, which macOS27, let alone '28 will not, there will be no OCLP for it...
It may be a while. They are still selling new M1 Airs through Walmart. These aren't grey market, they can still get Applecare.The real test will be when Apple will start dropping support for Apple Silicon Macs.
The bare minimum 1st gen AS MacBook Air is still a very capable machine today. At least with Intel Macs they have the excuse of wanting to ditch x86 once and for all, but now that Macs are on an architecture that Apple has complete control over, there's really no excuse to ditch anything so far.
And they've dropped the price even more from the $700 it was when Walmart first started selling them. I snapped one up at the time worried it was going to be a limited time thing and how fast inventory was selling but no, seems that they're still being churned out fresh for Walmart and presumably corporate accounts/clients.It may be a while. They are still selling new M1 Airs through Walmart. These aren't grey market, they can still get Applecare.
Shouldn't the question be: if developers aren't using the latest OS and XCode, how well do you think they'll support the current and near future version of the OS for their apps?If the developers are forced to use the latest OS, how well do you think they'll support older ones for their apps?
I'm using a MacBook Air that is just the version before (2017-19 and Intel). The thing runs swimmingly well, yet I can only upgrade to Monterrey (12). So far, I'm still on High Sierra and doing bloody fine. The problem is, Apple's hardware really deserves to keep going longer, as it is so darn well built. I can say the same for the 3 other vario-aging MacBook Pro's here.The real test will be when Apple will start dropping support for Apple Silicon Macs.
The bare minimum 1st gen AS MacBook Air is still a very capable machine today. At least with Intel Macs they have the excuse of wanting to ditch x86 once and for all, but now that Macs are on an architecture that Apple has complete control over, there's really no excuse to ditch anything so far.
I hope you're right. A quick glance at the Applications list in System Information shows that I'm still running quite a few Intel-only apps. Some of those are old apps I keep around (Divvy is a favorite), and nearly all the games I have installed are Intel only. But plenty of actively-developed apps are still distributed as Intel binaries, especially the ones in the "I use this because work requires it" category (why else would anyone use WebEx?). It's nice that I didn't have to think about this, but maybe that also means developers haven't worried about it either.Interestingly, I'm not sure it needs to be; Apple developed it in-house didn't they? The reason for pulling Rosetta was that the tech was licensed from Transitive: https://meincmagazine.com/uncategorized/2005/08/5195-2/ - since Apple owns the entire stack here, the only reason for pulling Rosetta2 is to simplify the stack and testing. Considering for Microsoft, the Intel translation layer in Windows ARM is still a major selling point, I can imagine Apple keeping it around for a while. If they don't, then they effectively lose the part of their market that is trying to build/test/run Intel-related stuff, which is MUCH more entrenched than PPC was 20 years ago.
Depends what you want to do with it. I have a similar MBA but 264 SSD instead. Everything else the same. I'm in the design biz and run Affinity Design software to create comps for design. This MBA works as smooth as silk. Still running High Sierra too.I have a pretty old Intel MacBook Air, 8GB RAM, 128GB SSD. What could I use this for instead? Any chance to install Linux on it and "do something"? Currently it's a literal paperweight on my very messy desk.
If Apple is constantly breaking backwards compatibility, that's their fault, not the devs.Shouldn't the question be: if developers aren't using the latest OS and XCode, how well do you think they'll support the current and near future version of the OS for their apps?
And now we know. It's dead for general purpose x86 apps after macOS 27.I hope you're right. A quick glance at the Applications list in System Information shows that I'm still running quite a few Intel-only apps. Some of those are old apps I keep around (Divvy is a favorite), and nearly all the games I have installed are Intel only. But plenty of actively-developed apps are still distributed as Intel binaries, especially the ones in the "I use this because work requires it" category (why else would anyone use WebEx?). It's nice that I didn't have to think about this, but maybe that also means developers haven't worried about it either.
I wonder what the space savings might be like when we no longer need universal binaries. I vaguely recall that being significant back in the Snow Leopard era, but binaries probably account for an even smaller share of an application's overall installed size than they did sixteen years ago.
Holy crap, I didnt even realize divvy wasnt being maintained anymore, just looked, the release we’ve all been running is 5 years old! I love the app, it replaced spectacle for me, guess now I have to worry about what to replace divvy with eventuallySome of those are old apps I keep around (Divvy is a favorite)
They make conversion kits to gut the motherboard and drive the still great displayThis is definitely making me wish they hadn’t discontinued target display mode: my 2019 iMac 5k could definitely use a faster CPU/GPU but the display is basically in like-new condition. I’d buy a Mac mini tomorrow if I could use the iMac as a monitor.
The bare minimum 1st gen AS MacBook Air is still a very capable machine today. At least with Intel Macs they have the excuse of wanting to ditch x86 once and for all, but now that Macs are on an architecture that Apple has complete control over, there's really no excuse to ditch anything so far.
...it's twelve years old, man.
I don't think it's exactly reasonable to expect a 12-year-old machine to be supported by current software.
Hopefully never. It's too useful for docker images that don't have an arm64 version.When will Rosetta2 be pulled? (The X86 translation layer for Apple Silicon Macs).
And they've dropped the price even more from the $700 it was when Walmart first started selling them. I snapped one up at the time worried it was going to be a limited time thing and how fast inventory was selling but no, seems that they're still being churned out fresh for Walmart and presumably corporate accounts/clients.
$649 for a new Apple laptop has to be a record low price even if the machine is rather old at this point
I get it, I really do... I still have a 2006 MacPro that I fire up occasionally to use a scanner that never got driver updates.I’ve already replaced it with an M2 MacBook Air, but I’m still kind of sad to see that I can’t even use it for Boot Camp anymore for those times where I need Windows for a specific piece of software.
I get it, I really do... I still have a 2006 MacPro that I fire up occasionally to use a scanner that never got driver updates.
That said, as cool as it is that it still runs, my statement stands; I don't see how any company could reasonably be expected to support 12-year-old hardware. Maybe my perspective is biased by having a whole stable of antique hardware (all the way back to a TRS-80 Model I), but I feel it's my responsibility to keep old stuff running.
Dude, it lived longer than an entire version of windows. It predated windows 10. Eventually requirements change, and after over 10 years I'd say that' reasonable enough. Nobody was putting windows 10 on a 2008 core 2 duo that ran windows 7 fine. Windows 10 was also a slowdown in major version changes, but if you look day one windows ten looked very different from day last windows 10 as it approaches. A lot changed without making a new full release likeh happened between vista>7>8>10 which launched in pretty rapid succession in about a ten year span. So your computer lived longer than the entire flagship status of multiple versions of windows combined in the end.I’m honestly more annoyed at Microsoft not supporting it anymore than Apple dropping support, because old hardware used to get supported by new Windows versions forever. Hardly anything that could run Windows 7 wasn’t upgradable to Windows 10.
They're being a bit more aggressive in the Intel to Apple Silicon then they were from the PowerPC to Intel era. There was a 6 year window between the release of the first Intel Mac OS, Tiger, and the first one to drop PowerPC, Snow Leopard.
Check your math... The first Intel iMac came out in January 2006, and Snow Leopard was released in August 2009.
You also have to take into account that the Mac OS X release schedule back then was not yearly, or anything close to it.Your OSes are off, but your timing is correct
Tiger: 2005, first Intel Mac was Feb 2006
Snow Leopard: 2009 (still had Rosetta)
Lion: 2011 (dropped Rosetta)
I don't think Batmanuel's point is that something running Windows 7 should be able to run Windows 11. (Correct me if I'm wrong.)Dude, it lived longer than an entire version of windows. It predated windows 10. Eventually requirements change, and after over 10 years I'd say that' reasonable enough. Nobody was putting windows 10 on a 2008 core 2 duo that ran windows 7 fine. Windows 10 was also a slowdown in major version changes, but if you look day one windows ten looked very different from day last windows 10 as it approaches. A lot changed without making a new full release likeh happened between vista>7>8>10 which launched in pretty rapid succession in about a ten year span. So your computer lived longer than the entire flagship status of multiple versions of windows combined in the end.