Marco Arment

And you can understand why, obviously.

That's an understandable reason why they would do that.

So what tends to happen on the Mac is whatever they need to do for iOS, the Mac kind of gets a half-assed version that doesn't have as many resources.

it's being applied to a kind of a more complex, more heavily legacy code base and, and software library and, and just a larger surface area in terms of like the needs it has to cover.

Like on the Mac, it's a huge surface area, way bigger than software UI has to cover on iOS.

Um,

But because it is lower priority in Apple, because it's not as big of a business, it gets fewer resources.

So it ends up getting fewer resources at a lower priority to solve what is often more complicated UI problems.

So as a result, Mac UI redesigns in the modern Apple era tend to be half-assed, incomplete, and not that great.

Again, also, those dynamics aren't going to change.

The Mac is not going to get a ton of UI design resources from Apple if iOS needs them first.

And iOS will always need them first.

And I think the whole idea that we need to unify everything about these platforms, not only I think is a bad idea for a lot of reasons, and I think it's misapplied in tons of ways because they're different platforms.

They work very differently.

They're used very differently in different contexts by different people.

So I think the idea that everything has to match between the platforms is like, I mean, look, the entire tech business is,

has tried this in so many ways.

The whole write once, run anywhere principle.

We've tried this so many times at so many levels, and it's either incredibly difficult or doesn't work every single time.

And so I think the reality of the Mac is that it will always be second priority in Apple compared to iOS in terms of software design resources and everything.