I feel like perhaps this is the wrong approach. Apple was once known for making ubiquitous hardware and software that didn't need a manual. So I view most IT to

I feel like perhaps this is the wrong approach. Apple was once known for making ubiquitous hardware and software that didn't need a manual. So I view most IT topics as anti-patterns that Apple should be solving rather than coping with. If I worked at Apple, I'd vote to invest more resources in fixing longstanding bugs. They make great stuff, but I've noticed a trend lately where nearly every Apple solution has a poison pill somewhere that makes it painful for a small minority of users and edge cases. For example: * Apple Time Machine does a 2-phase backup where the first phase is a "preparing backup" step that has no progress indicator, making it impossible to predict how long a backup will take. I've seen it take anywhere from a few minutes to days, meaning that if I forget to back up at the end of my workday, I simply have to skip it and swallow the anxiety unless I want to hang around for half an hour to back up 300 MB of changes. * iOS Safari added a search bar at the top for finding common tabs like "gmail". Which works great unless you have hundreds of tabs open, which requires scrolling pages and pages of tabs, and I've inadvertently thrown tabs away sideways as I was scrolling. A real solution here would be to make the search field available at any scroll height and/or provide a way to manage large numbers of tabs (which in fairness is an open problem, just like email). * iOS has an issue where Wi-Fi degrades after a few minutes/hours of use with various wireless routers, requiring the user to acquire a new DHCP lease (basically turn Wi-Fi off and back on again). I notice this especially with browsing social apps like TikTok or if the router's networking stack has gotten fragmented with UDP packets with P2P software like BitTorrent or video streaming. Apple needs to detect this and acquire a new DHCP lease automatically, rather than pretending that they don't have a problem. * External display support is hopelessly broken, especially with DisplayPort/HDMI dongles. I have a 50/50 chance of the left and right displays being swapped, regardless of which ports I plug the cables into. There's no debounce period between the time I connect a display and when Safari starts rearranging windows, so I literally have to remember to force-quit Safari before I pack up my work computer or it will lock up for many minutes when I connect it to displays again. I'd vote to scrap the code completely and start again from first principles, approaching it from a no-code perspective, and think about managing the display IDs as simple sets, falling back to heuristics in pathological cases like two or more displays having the same ID (which should never happen, but display protocols are hopelessly convoluted due to DRM and other concerns). * The on-off switch on Apple's wireless keyboard is atrociously unergonomic because it can't be used one-handed without sliding the keyboard into something (like a cup of coffee that then spills onto the computer). Also the anodized edge of the keyboard is so sharp that I accidentally cut through my front door screen as I was leaving for work one day. I could go on forever because like I said, so many of Apple's solutions have these poison pills. This is a tiny sampling of the things that cause me pain on a daily basis that I don't think will ever be addressed. I simply can't get into the myriad of issues with tons of other apps like Xcode, because that would fill volumes. Which is why I feel that Apple going the IT route will lead to further passing of the buck and stagnation, similarly to how Microsoft has struggled.