[dkonofalski]

I agree. I don't disagree with the fact that the OS and UI team seem a little less focused on the polish of the entire experience but the leaps in hardware are just too great to be able to keep up appropriately in the UI.

They really just need to get back to ironing out the every day things. Case in point - not being able to reply to a Message directly from the notification is a huge regression. Fix stuff like that first.

[skohan]

> the leaps in hardware are just too great to be able to keep up appropriately in the UI

Why would this be the case? Apple's a massive, well-resourced company and it seems like they should be able to walk and chew gum at the same time.

[mrkstu]

Microsoft and Windows Control Panel migration to System Settings argue its pretty difficult indeed, even for the most well-resourced companies.

[dylan604]

The failure of company A to manage a roll-out does not predict the failure of company B. It just goes to show how badly company A manages their resources.

[mrkstu]

Or, alternatively, that companies with large codebases face similar issues of complexity and legacy interactions that aren't easy to just throw people/resources at, they just take the time they take in order to get it accomplished and persistence is preferred over alacrity.

[dkonofalski]

This is just an opinion but I'm a big fan of Apple and have been using their machines for a long time. There are just some new conventions that have been introduced alongside hardware that add complexity that I don't think is possible to get right the first time around outside of some pretty minimum functionality. Any time an process needs to be re-thought or redefined, you're basically starting from scratch even if the end results look similar. In the example I gave, Notification Center was something that had to be ported over from iPadOS/iOS (and I'm glad it did as I find it very useful and much more consistent of an experience) but it then needed to be retro-fit to handle applications that weren't originally intended for it. It also needs to deal with notifications in a way that make them consistent so that new users pick up the basics of how it works easily. To me, that's a hard task. I just wish there was a bit more consideration taken towards keeping existing functionality in place, even if it contradicts new paradigms, but that's really a design choice that I just have to disagree with because the alternative is probably better for most people using the machines. If it's not, the analytics will bear that out and they'll change it to the one that I prefer.

[jbverschoor]

There are many things in macOS that have not been looked at properly. That has nothing to do with hardware. It's plain sloppyness.

[dkonofalski]

I disagree. I think it has everything to do with hardware because the software has to work with the hardware. The teams more than likely focus on making sure new hardware works with the OS as a priority and focus on the "nice to haves" for point releases. Rosetta, for example, probably took up a large chunk of time in the latest release and that has to extend to nearly every aspect of the UI to make sure that notifications, power management, and resource management all work properly with both new and existing apps on both ARM and x64 versions.