Most of the advantages presented in this post are going away, because the people left working on macOS do not have the resources to keep the features bug free. Drag and drop, for example, is not implemented correctly so that fewer and fewer drop zones get the right data type if at all or exhibit problems which look like there is a drop destination under the mouse but move the pointer only a pixel further and the drop just vanishes. Yes, vanishes, it doesn’t even perform the spring back animation. Sometimes though a ghost of the item stays on screen until the app where the drag started is relaunched.
4. Running uncompiled AppleScripts instead of opening the document in the editor application.
5. Ejecting one or all volumes.
6. Instant Open to profit from setting the system to a short key repeat and being able to open an item by simply dwelling on the last character a little longer.
7. Sub-Search puts large collections like emojis, bookmarks, and music into second row so that selecting primary items like applications and actions stays fast.
8. Instant Send allows me to quickly open the current Finder selection with an app that is not the default viewer or editor.
This. I feel like this is due to small shifts when lifting the finger. For the life of me, I cannot get myself to lift it like the testers at Apple do, and so I wished the product itself could go through learning phase; studying intentions and what actual touches happen.
Apple devs are probably doing something with the touch returned by the touchUpInside callback. This is an extremely, extremely common bug in iOS apps, not just with Apple developed software.
Devs love the symmetry of their touch handling code and often have the finger-down, finger-moved, and finger-up callbacks from the system all call the same handleTouch function they wrote. As you can tell, however, the touch from the finger up callback is often better discarded or handled differently otherwise you get these sort of bugs
Apple designers used to build interactive demos in Macromedia Director, so I'm assuming they knew a bit about scripting. That probably helped them think in a way that really clicks with software development.
I've worked with some younger designers who couldn't even put together a consistent click-dummy once the client wanted to see flows outside the happy path. To be fair, all they really had to go on was their education and Figma's panels.
The way I see it, money can’t buy one of the most important ingredients: the motivation to do the best work of your life. No matter how much cash you throw at a problem, you’re likely just going to get people who want to "do their job" from 9 to 5. Those are exactly the kind of workers that companies like the Apple of 2026 are looking for. It’s a big ship, and it needs to stay steady and predictable. People who want to achieve something "insanely great" or "make a dent in the universe" are just a distraction.
In my experience, shipping a product as polished as Mac OS X 10.6.8 Snow Leopard requires a painful level of dedication from everyone involved, not just Quality Assurance.
As long as neither the New York Times nor the Wall Street Journal writes about how bad Apple’s software has gotten, there’s even no reason for them to think about changing their approach.
The drama surrounding Apple’s software quality isn’t showing up in their earnings. And at the end of the day, those earnings are the "high order bit," no matter what marketing tries to tell us.
Well, if there's one thing history has shown us (including the history of Apple's own insurgency against the PC), it's that complacency and stagnation make the incumbent a target for every newcomer who does have the drive to make a dent in the universe. And there are always a lot of people with that drive. This is how we keep ending up in the cycle of chaos > new paradigm > perfect software that probably should not be improved upon > collapse under weight of new features > chaos > new paradigm... repeat.
Hmm. AppleScript? UI automation? Music.app? Smells like a waste of time. Besides *on* Apple Music suggests playlists formed from the whole Apple Music catalog. The code looks like it only handles songs that are already in your library.
reply