Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
From now on I'm going to consider the term unspecified bug fixes to either mean:

a) so many we'd rather not list them
b) so bad we'd rather not admit them
c) both of the above
For the last decade or so, I've taken unspecified "bug fixes and performance improvements" to mean 'no bugs were actually fixed' and Apple would rather obfuscate the changes with boilerplate most people are comfortable with than tell them the truth.
 
View attachment 2621156
Setting up new iPad today, 26.4.1 released whilst setting up. Failed to transfer data from iCloud, so had to erase and start again.
This was the keyboard layout, only after the second time as the first time it only showed 1/4 of the keyboard zoomed.

Absolutely mint system. Glad it’s so polished.
This is why we need that iOS 27 release. However, if this happens on the 26.4.1 version, who says Apple won’t introduce new bugs during the iOS 27 lifecycle?
 
From now on I'm going to consider the term unspecified bug fixes to either mean:

a) so many we'd rather not list them
b) so bad we'd rather not admit them
c) both of the above
or most likely: d) a flaw nobody has noticed before, maybe for years, but it's a way for a hacker to get into the system.

You don't want to tell hackers that an old OS might be vulnerable to some sort of attack. Better to be quiet about it.

That's the way my company handles vulnerabilities.
 
dear apple,

your base OS freshly installed weight over 150gb.
it is high time you get in touch with subtancial quantity of coffee, get a pulse, start to panic , raise the alarm, send everyone to battle station, now.
the situation, the qualificative for it is: appaling state.


( edit: i discovered i made a mistake in size calculation, the installed OS is *not* 150gb, but rather around 20-40gb . depending if you have dev stuff installed or not. apologies for the error )
 
Last edited:
  • Like
Reactions: MartiNZ and Morod
unless i'm mistaken, that's how i counted (with xcode removed):

Code:
[ kanzume ]
> du -sh /* 2>/dev/null | sort -h
  0B    /Volumes
  0B    /cores
  0B    /etc
  0B    /home
  0B    /tmp
  0B    /var
5.5K    /dev
2.1M    /sbin
4.1M    /bin
752M    /usr
2.1G    /Library
3.1G    /Applications
3.1G    /opt
 10G    /private
 33G    /Users
103G    /System
[ kanzume ]
>
 
Last edited:
  • Like
Reactions: capamac
From now on I'm going to consider the term unspecified bug fixes to either mean:

a) so many we'd rather not list them
b) so bad we'd rather not admit them
c) both of the above

Apple uses many open-source libraries in their OS packages, and those libraries frequently get updated with bug fixes. So Apple issues OS updates with those newer libraries included.

Easy to point fingers, but what you're pointing at isn't always the culprit. 😎
 
I was just updating my M2 MacBook Pro to this version & and it caused my Mac to brick itself somehow. Thankfully I have another Mac and it is currently trying to ‘revive’ the bricked one in DFU mode via the Apple Configurator. Hopefully it works.
 
  • Wow
Reactions: Morod
unless i'm mistaken, that's how i counted (with xcode removed):

Code:
[ kanzume ]
> du -sh /* 2>/dev/null | sort -h
  0B    /Volumes
  0B    /cores
  0B    /etc
  0B    /home
  0B    /tmp
  0B    /var
5.5K    /dev
2.1M    /sbin
4.1M    /bin
752M    /usr
2.1G    /Library
3.1G    /Applications
3.1G    /opt
 10G    /private
 33G    /Users
103G    /System
[ kanzume ]
>
That's not accurate. On the MacBook where I'm writing this, which has a 1TB disk, output of that command reports accordingly:
311G /Users
2.4T /System

Obviously there isn't actually 2.4TB of data in the System directory on this 1TB disk.
 
  • Like
Reactions: nsklaus
That's not accurate. On the MacBook where I'm writing this, which has a 1TB disk, output of that command reports accordingly:
311G /Users
2.4T /System

Obviously there isn't actually 2.4TB of data in the System directory on this 1TB disk.

that doesn't seem right indeed ..
i wonder why /System/ gets so high value? but i agree 2.4Tb size on a 1Tb dive doesn't look correct.

maybe some volume mounted in /System/ subdirs somewhere?
that would explain some..

if my method wasn't correct, then it would be nice to see a more correct way to check how much macos weights.

hmm .. i see preferences > general > storage
reports:
/System 25gb
/Applications 10gb
that would be a lot better but still a bit on the fat side.
i stand corrected, i made a mistake. thanks for the heads up. apologies for the wrong estimations on macos fatiness.
 
Last edited:
do you have lots of icloud space maybe ?
if there's a symlink in /System/ that point to user's icloud, that would be a way to explain it ..
for myself i have the default 5gb icloud space only
/System/Volumes is included in that so any external disks, servers, or mounted disk images will be in that count. A fresh install of 26.4.1 takes up under 20GB on disk, including all the applications. Because of how things are linked, the du -sh command just doesn't report accurate space usage.
 
For the last decade or so, I've taken unspecified "bug fixes and performance improvements" to mean 'no bugs were actually fixed' and Apple would rather obfuscate the changes with boilerplate most people are comfortable with than tell them the truth.

why would they push an update with no changes?
 
  • Like
Reactions: roncron
Why’s macOS so buggy then. Seems worse than usual.

interesting

I'm not having any noticeable OS issues at all currently

not saying they don't exist, I just don't have any current annoyances. frig, even mail doesn't crash on me anymore. and pmset works fine

those were long standing issues for me on Intel Macs, hackintoshes and carried on in to apple silicon

now that they just work I stopped thinking about them until I tried to think "what bugs am I seeing"
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.