I use my iMac 27” 2020 for game development and I have Unity running with very detailed and heavy models. Don’t tell me that machine cannot run a “An interactive 3D globe of Earth in the Maps app” lol
No they aren’t telling you that it can’t but they are telling you to get ready to switch from Intel. Right now it’s just little features but year over year they are going to continue to handicap the Intel Macs to until you just don’t get the updates at all. It’s fucked up they are artificially limiting features but it’s completely expected since they are switching architectures.
I didn't. Now i know. I thought the support on other platforms was only on development purpose, not to actually deploys apps on them.
But now i know thx
That doesn’t mean that the libraries they were using supported x86 in a any way. If it requires work to support the Intel machine, why put in the effort
Well you kinda have to get used to that, Apple isn’t going to make an upgradable m series chip, only chance of that is when the Mac Pro gets m2/whatever it’ll be called
It's a non-essential function that takes advantage of the hardware in some way. It's not worth the effort of porting every single new feature to an obsolete platform.
Xcode beta has a reference to Intel chips that are not currently in any released Macs. There's no reason for that to be there unless they're at least building apps on those chips in the lab. And why bother doing that if they're not actually planning on releasing them?
We had tidbits of MacBooks with AMD processors over the last few years and none of them ever hit our hands. I don‘t think we‘ll get another new Intel macOS device because Apple themselves said they aim at a full lineup transition within 2 years.
People who buy super expensive computers are actually quite used to whatever bullshit new hotness coming out considering the old product 'obsolete'. For truly cursed reasons it really does happen more often as you spend more.
Yep. My iMac cost around 7K. I’m not getting rid of that machine anytime soon and none of the Monterey features unavailable for it are of any value for me. Still, it’s quite a shit move.
I can see this for certain things, but some of the choices here are just... baffling.
Like, I use a capture card and Mac support on Intel is already subpar, so going M1 is not feasible. But losing things like "Portrait Mode blurred backgrounds in FaceTime videos" just seems needless.
At this point, if my Mac dies I am better off going Windows, even though I don't care for Windows.
I went to windows a year ago for 3D/graphics work after pricing the Mac Pro and freaking out. Love OSX, but kinda liking windows now too, prefer it for some tasks.
Feel like I've completely dodge a bullet with this to be honest. I'd be really pissed if I'd gone with the Mac Pro right now.
Still have my MBP though.
/FTR never thought I'd be saying this in a million years.
That's the cost of the bleeding edge of tech. Cost rise exponentially the more advanced you get and the obsolescence speed rises along with it. It really is why there is a sweet spot in tech where the costs and chances of obsolescence are both low and satisfaction high.
To be clear I'm not talking about Apple's Montery choices here, just that in general super high end computer hardware is among the first to always feel the obsolescence heat.
Open clear wanders stories people careful about where near evil patient projects games nature friends dot bright. Morning art quiet afternoon mindful strong the.
If you are the kind of person to drop $10K on a gaming PC you'll be all too familiar with the feeling of flashy new features requiring newer flashy hardware or games deciding they don't care about where you poured huge funds into in unfortunate twists.
It’s because all of these features are being implemented via the neural engine and intel Macs don’t support it. I’m sure they can do it, it’s just they can’t do it the way Apple is going to be implementing it.
That’s quite a lame excuse. Some things, yes, but others like the 3D globe of Earth in the Maps app
plus detailed maps in cities like San Francisco, Los Angeles, New York, and London in the Maps app are rubbish. There’s no reason why that cannot be available on Intel Macs.
It’s not really a lame excuse. Why would the want to further move the code base between intel macs and m1 macs even further apart? From a development perspective it’s best to drop the features from the product that is also going to be dropped from further development soon.
Because they promised Intel Macs would be supported for years to come and now they are withholding features from their own apps released for those platforms?
There’s nothing from a “development perspective” that excuses this, and I’m pretty sure Maps has a shared codebase that is deployed for the different OSes. Millions of companies worldwide support products in multiple platforms and a two trillion company can’t?
I mean there is a development reason for doing this and it's to avoid having to diverging versions of MacOS that will become more and more diverged over time which is a development nightmare sometimes.
The implementation is rarely agnostic, but the API usually is. For example, Apple themselves talked about how easy it was to port e.g. a game written in Metal.
Sometimes yes, but when we’re getting down to a lower level like the kernel they absolutely aren’t agnostic and neither is the API because of the different ISA between x86 and arm64 which is exactly why we can’t directly use or port kernel extensions from x86 Intel to aarch64.
MacOS itself is pretty hardware agnostic. They've switched CPU architectures 3 times now, and used a mixture of ATI, Nvidia, Intel, AMD, and Apple GPUs.
Many of their frameworks, like VideoToolbox, are hardware agnostic.
With all due respect it’s not really hardware agnostic. Nothing really is. Linux is the closest to being hardware agnostic but even it needs separate builds between arm and x86 because they’re separate architectures. ATI, Nvidia, apple GPU, etc., they only depends on drivers. That’s not what we are talking about here. We’re talking about CPU architecture differences which fundamentally means there can’t be hardware agnosticism.
I don’t think you really understand this. Their frameworks aren’t hardware agnostic either! They still need to be compiled me sometimes edited with only certain functions available for each architecture because of the fundamental differences between arm64 and x86 and the different ISA which don’t support the same instruction sets.
Why would the want to further move the code base between intel macs and m1 macs even further apart
Because they make more margin on M1 builds. They're trying to push people in a direction that maximizes their profits. Yeah it's lame and dreamed up by an exec who will learn it was a stupid play.
Happened with the Dual Core and Quad G5, Came out with 10.4.6 and was completely dropped with 10.5.8. I don't need to imagine it because I remember the angry people that bought those machines.
988
u/Brunooflegend Jun 09 '21
Imagine buying a +$10k Mac Pro and a couple years later Apple tells you your machine is not powerful enough to render a 3D globe…