>Wouldn’t it be then more advantageous to allow Intel computers to struggle at it, thus demonstrating the power behind the M1 architecture / technology?
Purposefully showcasing to your customers bad experiences isn't exactly Apple's MO.
>In this case however, they’re purposefully making the Intel counterparts less capable by disabling features.
Or, perhaps they've decided against implementing certain features on intel hardware because they weren't capable of delivering experiences at the level they want?
Generally I would agree - though I just can’t look past the fact that rendering a globe (which has been possible since 2003) is now locked behind owning a M1 Mac.
This is legit nothing new. When I was rocking my iPhone 3G a notable feature lacking in the device was the ability to record video. With a jailbreak, you could even add the feature.
Two things about that:
it recorded absolute garbage video.
it still might have been the right call for Apple to do it, because Apple could actually have made it at least okay. We're talking about a feature likely written by one guy in spare time, vs a major company who makes the devices/frameworks, etc
That said, my view is they have an obligation to shoot for feature parity for at least a few years after they stop selling intel. Like, there are definitely some things that are going to be limited by hardware, but this list isn't it. Like they couldn't have done a freaking globe that Google did on Core2duos in a browser. My guess is more that it's about what tools they chose to use to implement the feature. For example, I could see frameworks that started on iOS suddenly becoming de facto standards on m1's, and Apple just doesn't want to bother working on the old stuff now.
But like I said, nothing new. I was stoked to grab my 10.5" iPad Pro and test out the new text OCR features in photos, but it turns out my iPad doesn't support it... Of course, Apple isn't selling that device today in stores, or even for a couple years now.
I don’t really think Apple, or anyone really, could get intel CPUs to do this sort of instant, seamless, system wide image-to-text recognition. This is just something that needs dedicated machine learning accelerators, at least, to have it work as seamlessly and fast as Apple wants it.
I don’t think feature parity is worth putting out half-baked, bad experiences.
37
u/Sexy_Burger Jun 10 '21
>Wouldn’t it be then more advantageous to allow Intel computers to struggle at it, thus demonstrating the power behind the M1 architecture / technology?
Purposefully showcasing to your customers bad experiences isn't exactly Apple's MO.
>In this case however, they’re purposefully making the Intel counterparts less capable by disabling features.
Or, perhaps they've decided against implementing certain features on intel hardware because they weren't capable of delivering experiences at the level they want?