3 ms·
So the previously beloved mid-2015 MacBook Pro is unlikely to be compatible? Guess I'll keep it as a legacy machine running Mojave to run 32-bit apps.
by Apocryphon 5y ago
So the previously beloved mid-2015 MacBook Pro is unlikely to be compatible? Guess I'll keep it as a legacy machine running Mojave to run 32-bit apps.
- gambiting 5y agoTraditionally people have always hacked around these restrictions to make MacOS compatible with more Macs than apple planned for. Case in point - I still use a 2008 MacBook Pro, running Catalina. It works absolutely fine, despite this model not being officially supported by Apple for a long time now.
- arximboldi 5y agoHow did you do that? I'm interested...
- beermonster 5y agohttp://dosdude1.com/catalina/ http://dosdude1.com/catalina/
- mrweasel 5y agoMy late-2013 MacBook Pro isn't supported either, but Apple already said that Big Sur would be the last release for that model. I guess it will soon be time to look for an upgrade.
- pansa2 5y ago> Apple already said that Big Sur would be the last release for that model. They have? Damn. > I guess it will soon be time to look for an upgrade. But what to upgrade to? With no Boot Camp, the M1 Macs aren’t an option for me...
- mrweasel 5y ago> But what to upgrade to? I have have NO idea. I don't want the first generation M1, so I might just wait a year.
- toyg 5y agoIf you are running Big Sur now, you still have another full year (and a half) of support anyway. I'm still on Mojave because I don't want to lose 32bit games. I reckon that, as long as one stays away from Safari and uses an updated openssl for most things (e.g. via homebrew), the risks of keeping an old version running are minimal.
- pansa2 5y ago> mid-2015 MacBook Pro is unlikely to be compatible? Disappointing if true - they were still sold until mid-2018.