Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases macOS Sonoma 14.1
- Thread starter MacRumors
- Start date
- Sort by reaction score
It's simply not true that software quality has been on another level in the earlier SJ days. I could list some many glitches and annoying software bugs from the old Panther, Tiger, Leopard days that were exactly the same quality that we can experience today.
Sure, it always felt less buggy compared to the complexity that all the features in macOS, iOS etc cause today, but after all we've had enough bugs to deal with as well.
Starting my countdown timer now that x.1 has been released. If it can go a whole week without a bug fix (x.1.1), I’ll downloaded it and upgrade from Ventura
HobeSoundDarryl
macrumors G5
I'm getting weirdness when writing content for MacRumors replies too:
- Duplicate texts, even from prior posts (as shown in Mainyehc's pic)
- Text overlapping other text so I can't even read some of it
- Difficulty editing text
- Even as I type this, it is going in super-slow... so slow that if I move the cursor to another line to edit a misspelling, what I just typed will continue from where I insert the cursor instead of finishing where I wanted it to go.
Mac Studio Ultra running Safari 17.1
Any screenshots of this happening? I use safari non stop and would hate to update and get this bug.
HobeSoundDarryl
macrumors G5
So its not safari 17.1 or 14.1 particularly , just a bug that comes and goes
HobeSoundDarryl
macrumors G5
I'm using it on a hackintosh and I can't even get software update to see 14.1. I can get it to literally download the 12.12GB version from the Mac App Store but I don't want to go that route...
Before installing 14.1 my 2021 16" MacBook Pro, which is always plugged in, held its charge at 80%. After the update it's now charging to 100% and staying at that level. I'm hoping that it will revert to 80% charge shortly. Any one else seeing this?
It's back to limiting charge to 80%. Took 1.5 days to reset after the update.
It's back to limiting charge to 80%. Took 1.5 days to reset after the update.
Last edited:
automatic updates in system preferences?
or you could use teamviewer or something like that
That used to happen to me pretty frequently after OS updates back when I was still using a 2018MBP (I've now switched to a Mac Studio) and - IIRC - the issue usually went away after two or three days. I assume it's because all of the restarts associated w/ OS updates kind of throw the whole optimized charging schedule out whack for a bit but I could very well be wrong about that.
I'll be waiting another several months for all the bugs to properly clear out. Somewhere around version 14.3 or 14.4 should probably do it.
To conservative from my viewpoint but I have heard,”install a major update (iOS 14), only after the release of the 1st beta of the next major revision (iOS 15)”
Depends. How bad do you want the new "features"?
These days, each new release of macOS is pretty much a yawn event for me. I only update to vaguely keep up with the security updates, and because some software requires newish OS versions.
I was, quite frankly, quite satisfied with Mojave, and would happily still use it if I could.
I've been using Macs for almost 20 years (i.e. also since Panther; I did use Jaguar for a few days, as it came preinstalled on my first Mac, but it came with pack-in Panther upgrade DVDs which I made use of shortly after), and… I actually disagree.
Yes, I remember suffering from my fair share of bugs, graphical glitches, etc., but they were somehow… more benign. Even the great debacle that was the loss of functionality in iWork or in Final Cut Pro, when Apple rebooted their respective codebases, felt less gratuitous or disrespectful, because there was some sort of a program behind it and it WAS properly communicated to the end-users, even at a time when Apple's PR was a bit of a paranoid mess.
These regressions and silent feature deletions, half-assed implementations (like the CloudStorage framework and the world of hurt it wrought upon us, in my case as recently as… you've guessed it, the 14.0 update, which borked Time Machine in the process because of some really stupid decisions made by Apple engineering) and whatnot do feel a bit more sloppy and egregious than before. Back then Beta builds felt like Beta builds and RCs and GMs felt like RCs and GMs, whereas now everything feels like Beta builds, one after the other, with many old bugs left unfixed and new ones, including regressions, unannounced feature deletions, etc., rearing their ugly head.
For sure, I remember some infamous bugs like the one that caused data loss on external media connected during OS updates (was it some Leopard point update in the later G5 days? Maybe…). Yes, Apple did have some really dark moments in the past, but their current crop of software, especially on the Mac, gives off that “death by a thousand cuts” vibe so familiar in Microsoft products of yore (and current ones, as I've been sadly also realizing, and likely for similar reasons). I remember vividly what using PCs was like, and the kinds of issues I've been getting on the Mac remind me a lot of those. Especially the cryptic, non-human-readable/fixable nature of some of the structures put in place by Apple on top of NeXTSTEP/early OS X's simple elegance.
Apple engineering moving away from the com/org.[app developer].[app name].plist naming scheme and simple Application Support/[app developer]/[app name] hierarchy to whatever the hell they decided to come up with on their Containers and Group Containers folders is ridiculous (yes, I get it, it has to do with sandboxing, but… did they *really* need to add a numerical identifier for developers? Why didn't they use a similar naming convention to that of .plists and add such identifiers after their names, so as to not screw up alphabetic sorting, then? 🤦♂️), and the insanity that is TCC reeks of both Vista's UAC at its worst and, to add insult to injury, the Windows Registry itself. Trying to troubleshoot and fix TCC permission-related problems feels like complete voodoo, with some of those probably calling for an outright erase-and-install (seriously, at some point it may just be easier, and kind of makes me miss editing hex values by hand). Don't believe me? The fact that this page even has to exist (or, better yet, that a regular user might have to resort to it) in the first place is a bit worrying if you ask me.
TL;DR: it's not just the bugs, it's the inelegant way the OS is structured, and that unsettling vibe of technological debt slowly but steadily accruing. Yes, I know Apple has been “replacing parts of the engine while in flight” for a few years, but they've also been tacking a lot of cruft on the side (will you look at all those daemons in Activity Monitor, trashing your SSD and whatnot), and even when it's patently useful or even essential, it isn't nearly as elegant or well thought-out as early OS X components and structures were. It's hard to put a finger on it, but modern macOS, at least behind the curtain, kind of feels like a weird blend between the worst of Windows, Classic Mac OS and even OS X (namely its lack of transparency whenever something goes wrong, which has indeed been a longstanding problem), with but a veneer of user-friendliness on top.
Last edited: