We need a new "snow leopard" release. No new features. Cleaning up the mess. Ethically speaking, there's no excuses for Apple. They're sitting on a huge pile of resources. Don't have the team competent enough to handle stuff? Hire them. Yet I know that's not how capitalism works.
As someone who witnessed a lot of the quality decline at Apple from the inside, hiring more people is decidedly not the answer. All that does is encourages management to engage in more churn, which is the source of these sorts of bugs.
The answer, unfortunately, is that features need to be sunsetted/removed, the engineering org shrunk, and for a smaller group to concentrate on a reliable product core.
It's not about the sheer numer of people, it's about their quality as managers, engineers, art directors and designers. Hire the best, pay them accordingly. Things can thrive without austerity, given enough good resources.
I disagree. A lot of the problems come down to part A of the system not coordinating well with part B. Take the brouhaha about the Tahoe window corners: obviously there wasn't enough communication between folks designing the window frame art and the folks implementing the window resize logic.
You can hire the best, but coordination among a group of people scales quadratically.
I'm really surprised they don't attempt to make the Mac a more work-focused machine.
Try building a graphics editor in SwiftUI. This is not really possible in 2026 in SwiftUI. I build a zoomable pannable page setup was incredibly difficult but possible.
Then try adding WYSIWG text editing to that. I got halfway to building one using CoreText to render to Canvas which works but then there's this fight with their NSAttributedString which is opaque and horrible, making it impossible to store CMYK colours alongside the text runs. There's also no way to capture iPad keyboard input in SwiftUI.
In the end, I have to build things that fit within platform constraints if I want to use SwiftUI.
The fact that e.g. Canva and Figma bypass almost all their APIs and draw to canvas should be a wake-up call for them.
Also PDF generation is painful enough that I'm considering a Java based web-service for document export on macOS.
I especially love the "Methodology" block at the bottom of the diagrams, which seems present only to add an air of authority, but all it really says is that they picked the flagship phones of each brand.
Now that I think about it I saw a twitter thread the other day about a series of garbage vomit SEO gibberish, all using same template with very prominent Methodology/references section. Might be something new Google is sensitive to and seo people picked up.
The biggest mess IMO is the media library. Unsustainable, chaotic, impossible to keep in order if you happen to publish more than just a few images.
It’s not a library. It’s a file dump. If you want to reuse an asset on a non-trivial site, it’s easier
to reupload the file rather than to find it in a flat list of thousands of thumbnails.
Folders, please.
And the four hopeless fields to provide an image with textual metadata (alt, caption etc). It’s impossible to understand intuitively. So anti-human, lacking understanding of what users need and are capable of grasping.
Reveal the complexity gradually, please.
Same goes for the myriads of options (special love goes to the media link/image size selector with its thoughtless defaults you have to scroll down the media library modal to even reveal itself) just to insert an image into the text.
Folders are something that's been needed in WordPress for 10+ years and hasn't gained any traction. It's to the point where it's beyond terrible and is a large reason I don't use WP anymore.
Folders have problems too, inflexible and depend on people managing them well. If the team can’t be bothered to namespace files and fill in metadata properly, I doubt they will manage folders well either.
It’s 2022. There’s got to be something more sophisticated than folders, something content-aware that reliably finds the desired image in the library and suggests it when someone tries to upload a dupe. How do we have computer vision reliable enough to recognize people on our phones and steer a car, but we’re still relying on metadata and folders to find images in a web CMS?
But the truth is, storage is cheap so there is no compelling reason to solve this problem. If the site ends up with 27 copies of the same JPG, who cares? Oh no, we used 30MB we didn’t have to.
That does not make sense to me at all. As a single user, where is the relation between "namespace files" and "metadata" when all I want is to upload some images to a folder named foo or 2022?
I'm not saying there isn't a better solution, but other blog/cms applications could do folders without problems 15 years ago.
We have over 8000 images and growing. If you name them properly and use alt text the searching works okay. But we also don't reuse images that much (not because they are hard to find)
Since it's mediawiki we can view the history of updates; Having less than 5 updates every year means this is probably only an afterthought when someone comes across an "are we ... yet" site. There's not someone at Mozilla whose only job is to track them down.
What suggests to you that those were "resources working on this" and not just people, inside or outside of Mozilla, doing that because they thought it was funny or interesting?
