I like it. Debacle isn't the word you're looking for. "Some loud people on the internet don't like it and the user base has largely been ambivalent towards it. In reality, it's rough around the edges and needs some work."
Comparing Tahoe to Windows 7 is hyperbolic. 7 had Media Player, 8 had Groove Music. 7 was welcomed as a feature-rich upgrade, 8 was boycotted as a user-hostile downgrade.
I don't know what school of contemporary design you hail from, but you can't piss on my back and tell me it's raining. Liquid Glass needs an 8.1 update, at the very least.
The Windows 7 vs 8 analogy doesn’t support your argument, it undermines it. Windows 8 wasn’t disliked because it was “modern”, it was disliked because it broke core interaction models in a way that actively obstructed use. macOS Tahoe hasn’t done anything remotely comparable. No Start screen catastrophe, no forced touch-first UI on non-touch hardware, no fundamental workflow regression.
What you’re reacting to is aesthetic drift, not functional decay. Liquid Glass is a visual language experiment, not a UX rupture. You may dislike it, that’s fine, but equating it to Windows 8 is category error. One is a design iteration layered on top of a relatively stable interaction model, the other was a structural interface failure.
Also, invoking Media Player vs Groove Music as if those are meaningful historical markers of “user-hostile downgrade” is... generous to the point of fiction. Windows 8’s problem was input metaphors, not media apps.
This isn’t Apple becoming Microsoft. It’s Apple doing what Apple always does: overreaching aesthetically, then sanding it down in point releases until everyone forgets they were angry in the first place. Which, incidentally, is exactly what happened with Aqua, iOS 7, Big Sur, and every other supposed apocalypse.
Howard Oakley has been writting about macOS internals for a long time, and 99% of the time, his essays and articles are excellent. This is not one of them. Don't be put off by this one article - the site is a goldmine.
The people that certify it say that you are wrong. What you think and what actually is are two entirely different things in this case. The fact remains that, according to the OpenGroup (and they are the one that matter here), macOS 26 is UNIX.
macOS 26 that is /altered/ is UNIX. macOS that ships on every Mac is not certified UNIX -- but it can be made to match if you're willing to give up security.
You’re confusing operating mode with operating system.
SIP/SSV don’t create a different macOS, they restrict mutation and introspection. They don’t change the POSIX surface, the SUS semantics, or the kernel interfaces being certified. They just stop test harnesses from instrumenting the system without elevated privilege.
By your logic, no modern OS is anything it claims to be unless you run it in an insecure debug configuration. Linux isn’t POSIX because you need root. Windows isn’t Windows because kernel debugging exists. That’s obviously nonsense.
The Open Group certifies macOS 26 as shipped. Temporarily relaxing protections to run a conformance suite does not produce a “different OS”, it produces a different trust configuration of the same one.
Saying “it’s not really UNIX because SIP is on” is like saying a container isn’t Linux because it doesn’t let you mount /proc without extra privileges.
You didn't read the article, did you? SIP isn't the only alteration. And we don't know all of the changes required due to the waivers.
> if you want your installation of macOS 15.0 to pass the UNIX® 03 certification test suites, you need to disable System Integrity Protection, enable the root account, enable core file generation, disable timeout coalescing, mount any APFS partitions with the strictatime option, format your APFS partitions case-sensitive (by default, APFS is case-insensitive, so you’ll need to reinstall), disable Spotlight, copy the binaries uucp, uuname, uustat, and uux from /usr/bin to /usr/local/bin and the binaries uucico and uuxqt from /usr/sbin to /usr/local/bin, set the setuid bit on all of these binaries, add /usr/local/bin to your PATH before /usr/bin and /usr/sbin, enable the uucp service, and handle the mystery issues listed in the four Temporary Waivers.
Don't be rude. I did read TFA, hence my comments. You didn't understand my comment, did you?
Whether it disabling SIP, enabling root (see the bit about Linux and Posix in my previous comment), enabling case sensitivity in APFS (done for backwards compatibility), or any of the other stuff, the OS shipped remains the same as the tested one, and pay attention because this is the bit you seem to be incapable of grasping, with the extra bits turned on! Some are dumb, some for backwards compatibility and some are genuinely useful.
A Kia Ceed is still the same Kia Seed if the showroom add their stickers, changed the tyres and put some registration plates on it.
It is. Add we all have off days. Perhaps Howard has had one here. I mean, he is defining what type of OS it is by how it's configuted. Which is just wierd.
I got a chuckle out of that for my own reasons as a long time Mac user as “Mac OS X is Unix” was the brand back in the 10.0-10.3 days, to the point I believe they got a Unix certification by someone, and then again with macOS 15 they got an Open Group UNIX certification.
Funnily enough, they had no certification and weren’t compliant in 10.0-10.3 days, so what they were doing was trademark infringement, hence the lawsuit from the Open Group. 10.4 was the first compliant version. And oh boy they really milked it for several years afterwards.
Blender is an interesting case. It's seeing wider adoption in studios generally - an Oscar win has helped and the recent Blender Conference had talks from Framestores vizdev[1] and Paramounts in-house teams[2]. Blender 5.0 is around the corner, which is adding more and more industry standard features[3][4], though recently there was a discussion about pulling away from the VFX Reference Platform[5][6], which they have walked back from[7]. It's not there yet, but it's gaining mindshare rapidly. Enshittification in DCCs is interesting. Arguably the two dominant companies, Autodesk (Maya, 3ds Max) and Maxon (Cinema 4D) are on that path, whereas SideFX (Houdini) is kicking ass!
At least he was consistent and the UI design made sense, textures aside. And UI gossip aside, all the accounts from every engineer who worked under him consistently praised him.
Safari with its KHTML underpinnings was also created under his watch, apparently.
Webkit (along with Safari) was started under Avie Tevanian's watch. Scott Forstall worked under him and Bertrand Serlet, along with Lisa Melton, who lead the development team for Webkit. Forstall was responsible for the development and release of Apple Maps.
And for Apple Maps, I remember reading somewhere that one reason Forstall refused to sign the infamous apology letter was that the initial release was from a team not directly under his supervision, but I can't find the old reference to that...granted, whatever went down was probably a joint failure of everyone involved
Not that OS9 was better - there are thing that I miss, such as drag and drop control panels and system extensions. My point is that people have been complaining about the newer versions of Mac operating systems since there were numbered upgrades.
reply