A fight for attention by a specific, resource-starved macOS engineering team could not be more incorrect. That’s simply not how Apple works. You have to come up with a different explanation for these perceived quality problems.
The developmental move to agile deadline-driven feature-sprints under Craig Federighi.
The way to think about this is that the menu bindings are AppKit features which share resources with UIKit.
An interesting theory would be one which identifies (i) who in the organization gets to gate what ships and decides it’s good enough (ii) what are their incentives. At a company like Apple which is huge, has marketing deadlines, and is coordinating hardware, software, and services releases, both items have very subtle and interesting answers.
I've also experienced very few bugs in MacOS which have affected me on a day to day basis. Not saying they aren't there, but to me the MacOS team are doing a pretty great job.
In particular, zoom.us, our teleconferencing solution, crashes them regularly with spewed messages about GPU stuff in console. We're about at the point of running windows vms so my salespeople can have a reliable conferencing solution.
The keyboards also do not hold up at all. I've gotten into a shouting match at an apple store after buying their "warranty" and learning that a keyboard repair would mean the laptop would disappear for a week. That's not a warranty; that's some Dell consumer-grade bullshit. I basically had to buy a floater laptop on the spot. Two of the laptops, including my cofounder, have keys that don't work, but they're too busy to deal with Apple's bs to get them repaired. I'm aware that after the WSJ embarrassed them the wait is supposedly shorter, but it's not anything reasonable. They should be able to do a keyboard swap in an hour while you wait.
Their busted ass OS also has automatically (!!!) disabled Filevault, refused to turn it back on, including spending 6 hours on technical support and an OS wipe. We had to take that laptop into the mac store for them to service. Folks, don't wait on installing an mdm -- just because you turn Filevault on, it can silently disable itself.
Apple's keyboards used to be excellent. After the new keyboards came out a few years ago they've been delicate (I've come around on my opinion about how they are to use--but I'm still not a fan of the layout). Replacing them is also a nightmare. So far a keyboard cover has seemed to not have me baby it and prevented a repeat of any issues.
For consumer grade stuff, I'm not a fan of Dell. But their business laptops and support services are solid, from what I've seen.
I haven't experienced any of the other vendors, but any vendor with a business line (such as HP or Lenovo) have similar support services. And just as critical: they design their business laptops with that need in mind. If you pay for a service level that includes on-site support, very few issues are un-repairable by a field technician. And they even make access to things like the hard drive easy, since corporations don't like to relinquish control of potentially sensitive business data.
Apple offers enterprise support[2] (not sure if that's an indication that the service is priced out of the SMB range) with similar onsite services. But their machines aren't exactly designed to be easily repaired. So if an Apple Store would have to send it off to a repair depot, I doubt a field technician would be able to do much more.
[1] https://www.dellemc.com/en-us/services/support-services/pros...
The MBP I had previously (same model, exchanged out due to keyboard keys sticking) did the same thing.
Additionally I find if the battery hits 5%, it doesn't actually register that it's charging in time to save it. Fair enough, but call it zero (so implicitly I'm warned earlier).
- I upgraded to 10.13, and my stock graphics cards would slow, freeze, and then crash window server, logging me out. I spent the money to buy a hot new GPU from Apple's latest recommendation list, and it no longer crashes (though I'm having trouble getting both of my Apple displays to work, since apparently most of the "DisplayPort to dual-link DVI" adapters in the world are actually single-link).
Other issues I've run into recently with new or revamped features:
- Dark mode works great sometimes, and other times it's an unreadable mess.
- Xcode 10's new text editor broke control-T, which has worked correctly in every text field since the earliest days of Mac OS X.
- The new security around contacts/calendars broke my app. It doesn't work like it used to, it doesn't work like the documentation says it should, and it doesn't log anything useful to help diagnose the problem.
- The recent documentation, overall, is a big step down. developer.apple.com used to have long-form articles describing how things were built. Now, it's mostly just HTML versions of header files, and half the descriptions are "No overview available."
- The new WKWebView teases improved performance (and not being deprecated, like WebView), but removed major features I was using, or planned to.
- Dragging toolbar items in Safari 12 seems completely broken.
- You can set almost any accessibility option via script, except menubar transparency, for no apparent reason.
It was no coincidence that Macs used to be simple. "Simplicity is prerequisite for reliability"! When you've got only one color scheme, you can make it 'just work' everywhere. Once you've got more than one color scheme, now you have to go check everything to make sure this doesn't happen: https://twitter.com/KenHatesSoftwar/status/11059512173713530... (which depends on the dark-mode setting, the reduce-contrast setting, the desktop wallpaper setting, ...)
Multiply this by every permutation of settings. I don't think it's feasible any more for single-developer Mac shops. There just aren't enough hours in the day to make everything work well. Even Apple is struggling.
My next project isn't another Mac app. It's a web app in Clojure. CSS is still terrible to work with, but (with grid and flex) it's slightly less awful than it used to be, and much more consistent. And Clojure is infinitely more pleasant than Swift.
I couldn't believe this, so I tried it. To clarify: in Xcode 10.2.1, typing control-T between two characters in a line exchanges the two characters, as expected. But typing control-T at the end of the line does not perform the special case of exchanging the two characters at the end of the line; instead it exchanges the last character of the line with the newline, thereby moving the last character onto the next line. Off to bugreporter...
Yes, there is feature creep and it does have a bit to do with executive mind-share. But don’t attribute to greed what you could attribute to the age old problem of managing software complexity.
The way to win the game is to not play.
In the Scott Forstall days, there was a distinct iOS team (Scott) and a distinct OSX team (Craig). now there isn't.
Frankly, maybe that's exactly the problem. He left in 2012, and that definitely feels like around when things started going downhill.
I don't know what stuff is like under the hood, but from a user perspective, iOS and macOS are two very different platforms that are good at very different things. I'm sure there is a lot of tech that can be shared between them, but some individual focus would likely be beneficial as well.
And if those "other responsibilities" are iOS, tvOS, and watchOS, then there is no "macOS team." There is the software engineering organization.
Apple slices up departments by function, not by product, which is why there are organizations under Tim Cook such as Software Engineering, Hardware Engineering, Internet Services, etc. Everyone and no one is responsible for shipping all the products as a result of this structure. Software Engineering in particular is responsible for all of the operating systems that powers Apple hardware.
Similarly, this is how smaller departments under each SVP/C-level org are subdivided, and so on to the team level. Each team may be responsible for a particular product, which includes all the experiences for that product across operating systems. There is no single engineer responsible for just macOS/iOS/tvOS/watchOS. Everyone is responsible for everything, and similarly no one is responsible for anything.
Apple's structure is unique compared to other companies, and contrary to how most are run, which probably contributes to your confusion.
Apple is a phone manufacturer. Computers are a side business.
But given that developers have no choice in the matter, they’re stuck putting up with whatever issues Apple doesn’t bother to fix. I’m sure Apple is well aware of that when prioritizing what bugs are important.
[1]http://cdn.arstechnica.net/wp-content/uploads/2016/04/Apple-...
I get that Apple makes more revenue from other products, but the Mac is still extremely profitable. They ought to give it some attention on those grounds, if nothing else.
Every OSX engineer probably has more bugs on their plate than can be fixed in one career, in addition to feature development tasks. The OSX team is severely understaffed both because it is not a priority at Apple, and because it is getting harder and harder to find engineers that are able to/willing to work on this kind of code - a Byzantine labyrinth of C flavors that's been accreting lines for decades.
The OSX team is in a desperate fight for recognition and status against the iOS team. They believe (and are probably right) that the only way to gain executive mind share there is to build out new visible features, no matter how useless. Witness dark theme, stacks, dynamic desktop, siri on the desktop, a steady stream of useless iPhone integrations, etc. All the troops are ordered to march relentlessly toward feature development. Stability and bug fixes be damned.
It bet it takes at least three weeks of focused effort and red tape macheteing to fix this bug and it is way down on someone's list. Even if you fix it the change won't make the next OSX key note at the annual IOScon or whatever it is called, so it won't help your career one iota.
Again - this is just how I imagine it is there. I don't really know.