Same, no issues. But our use cases may be different than some of those complaining. I’m all for stability updates, because one day I may be one impacted by rushed updates.I’m on 12.5.1 with my M1 MBP 13. Everything is fine. You people are crazy.
Same, no issues. But our use cases may be different than some of those complaining. I’m all for stability updates, because one day I may be one impacted by rushed updates.I’m on 12.5.1 with my M1 MBP 13. Everything is fine. You people are crazy.
Honestly, I wouldn’t be surprised if we see that in the next year or so. iPhones are so expensive, with such small changes, and completely saturated smartphone market.He isn't wrong. MacOS today is less polished than it would have been in 2000. There is always something that doesn't work right or some huge bug. The Apple apologists always have some "Apple does no wrong " angle to counter it with. The sad reality is that Apple doesn't have to get it right anymore. The Mac is not the main source of revenue, nor is it shipped on CD. The "release now, fix later" business model is the new standard unfortunately. Lack of competition and not caring about Mac market share means MacOS will remain a dumpster fire. It's just not a top priority. Everyone is working on questionable inclusive emojis for iOS as that is where the money is. Maybe when the iPhone revenue starts declining they will care.
Just because your experience with Monterey is 'a dream' doesn't mean everyone else's is. How is it nonsense if we are experiencing it?Monterey is a dream to use. Go wherever you want but stop your nosense.
It seems like you might've run into the same issue I did with port forwarding. Works fine in Big Sur, completely broken in Monterey. It's a niche use case but still a shame as many developers rely on Macs.I have been a macOS user since the first appearance of MacOS X. After the initial start, macOS became a platform that I loved not just for the experience, but for its stability and performance. I would easily have a laptop running for many months without single reboot and without problems. I am reasonably technical (having been part of a team that won an Apple Design Award once) and I know my way around the lower levels of the OS. There too I could do the things I should be able to do and 'it just worked'.
The last years, my experience has been completely otherwise and I've reached the end of the line. A few months back I decided to move my older macOS versions (one Mojave and a few macOS Catalinas) to macOS Monterey and, boy, do I wish I had never done that (in case of Mojave, I really wanted to because there were no longer security fixes).
A list of issues I encountered in various versions of Monterey:
And this list isn't even complete. macOS Monterey 12.5.1 in my experience is as buggy and fragile as anything I have ever had to work with in decades, and that includes older Microsoft Windows. This is now especially the case with anything having to do with sockets, ports, traffic, etc., i.e. kernel level stuff.
- A 4K LG monitor that isn't recognized as 4K but as 5K. Notable: that same monitor is recognised fine on the only M1 Mac over here. Note also: I have 5 different Macs in this household, this clearly is not a hardware problem if all the Monterey x86 Macs do not recognise the monitor correctly, but the same hardware before the upgrade did, the only x86 Mac still running Big Sur does, and the M1 Mac running Monterey does.
- A monitor that directly after the 'upgrade' on a Mini was only showing black until after an SMC reset, a problem that returned a few times
- If Display user preferences are set, it might crash WindowServer making it impossible for that user to log in (log in, Window Server starts up, crashes, back to login screen). I had to go in via another user, clean out the affected user's prerefences, after which logging in was possible again (though all preferences were lost)
- Booting a system with a USB SSD attached (SanDisk) via USB ends up in a situation that the whole disk isn't seen (missing from System Info) until you physically disconnect/reconnect the drive. Two Thunderbolt drives connect fine and so does a USB RAID
- Attached wired keyboards/trackpad (all Apple) unable to wake a system from deep sleep, you need to physically disconnect/reconnect them to get them recognised
- A monitor as second monitor on an iMac. When the monitor is turned off, the main screen works but input (trackpad, keyboard) gets stuck for a half-second or so all the time.
- If you use software that allows connections from the outside and you use the Application Firewall (ALF) to protect your system, at some point using ALF meant that a certain service would stop working after a few hours because the kernel had stopped passing connections on to the software. Stopping and starting the software made it work again for a few hours. This software ran fine under Mojave and several earlier versions. It seemed that the kernel ran out of resources and that stopping and starting the software freed them. I had to stop using the firewall as a result.
- Services that are started by hand work fine, but when started via launchd are unable to reach.
- And the latest: under 12.5.1 the system suddenly freezes for all connection requests (e.g. you cannot ssh in to the system, or use ARD, etc. Nothing that requires TCP/IP it seems. Ping works, but no TCP/IP port can be reached. Most of the time, this will resolve itself after a while as if the kernel gets 'stuck' and at some point gets 'unstuck', but sometimes it doesn't and you have to hope you are logged out and can click the restart button or you have to do hard reboot. The last time an unstuck happened after an hour or so.
I have my suspicions about what may be in play here:
Apple has always been that weird combination of 'insane level of attention to detail' in one place and 'insane level of neglect' elsewhere. But I have to conclude that now that Monterey is at version 12.5.1 it still is buggy, fragile, unreliable. It is a P.o.J. and I am very sorry that after more than 20 years of Apple use I have to give up on ever having something as robust as it was years ago. And the history of recent versions have been that they have become worse and worse in terms of reliability over the years.
- Apple not spending as much energy on x86 as it does on M1 (which pisses me off as I spent thousands on all these machines)
- Apple working hard on adding security (e.g. the kernel being able to merge a read-only and writable volume into one file system, very neat, and a lot that is now connected to software being signed) but not doing a very good job at writing correct code that can handle all the different situations ('happy flow code')
- The 'unstuck' behaviour of 12.5.1 really feels like Apple has put in some stopgap measure to make sure that if the system gets stuck there is some sort of low level 'reset'. Or, Apple knows this is unreliable, but has implemented some sort of garbage collection that once in a while cleans stuff up so it starts working again
I have started to investigate moving parts of my (until now 100% Apple) landscape to another OS because the level of reliability has become so low that I have lost my confidence that it will be reliable any time soon.
You can see from the sheer number of "likes" in this thread that it is hardly nonsense. Indeed, there's a thread with more than 600 responses solely about issues with the Music app, let alone the rest of the system.Monterey is a dream to use. Go wherever you want but stop your nosense.
Me: decides to finally update the boot SSD with MontereyBooting a system with a USB SSD attached (SanDisk) via USB ends up in a situation that the whole disk isn't seen (missing from System Info) until you physically disconnect/reconnect the drive. Two Thunderbolt drives connect fine and so does a USB RAID
I'm always happy to hear of people who enjoy their Macs and the OS they are using. However, we both seem to agree that not every experience is as great as those that boast or simply share their good fortune story.Just because your experience with Monterey is 'a dream' doesn't mean everyone else's is. How is it nonsense if we are experiencing it?
I would say no. The vast majority of the bugs are in what is almost certainly high-level (architecture-independent) code. While there are undoubtedly some Intel-specific and Arm-specific bugs, many of the reported issues can be replicated on both types of system. It's the code, not the CPU.Will the bugs stop when the transition to ASi is complete?
I migrated to Mojave a few months ago from Sierra. It's been solid for me also. Prior to that, it was Snow Leopard. I realize I'm way behind with security updates but if nothing compelling is offered in the next macOS, I skip it. I no longer trust Apple's annual releases with respect to stability.My main computer is a Mac Pro stuck on Mojave and it’s bombproof. Never a single issue.
I have started to investigate moving parts of my (until now 100% Apple) landscape to another OS because the level of reliability has become so low that I have lost my confidence that it will be reliable any time soon.
don’t do it. Already did this many times.I have been a macOS user since the first appearance of MacOS X. After the initial start, macOS became a platform that I loved not just for the experience, but for its stability and performance. I would easily have a laptop running for many months without single reboot and without problems. I am reasonably technical (having been part of a team that won an Apple Design Award once) and I know my way around the lower levels of the OS. There too I could do the things I should be able to do and 'it just worked'.
The last years, my experience has been completely otherwise and I've reached the end of the line. A few months back I decided to move my older macOS versions (one Mojave and a few macOS Catalinas) to macOS Monterey and, boy, do I wish I had never done that (in case of Mojave, I really wanted to because there were no longer security fixes).
A list of issues I encountered in various versions of Monterey:
And this list isn't even complete. macOS Monterey 12.5.1 in my experience is as buggy and fragile as anything I have ever had to work with in decades, and that includes older Microsoft Windows. This is now especially the case with anything having to do with sockets, ports, traffic, etc., i.e. kernel level stuff.
- A 4K LG monitor that isn't recognized as 4K but as 5K. Notable: that same monitor is recognised fine on the only M1 Mac over here. Note also: I have 5 different Macs in this household, this clearly is not a hardware problem if all the Monterey x86 Macs do not recognise the monitor correctly, but the same hardware before the upgrade did, the only x86 Mac still running Big Sur does, and the M1 Mac running Monterey does.
- A monitor that directly after the 'upgrade' on a Mini was only showing black until after an SMC reset, a problem that returned a few times
- If Display user preferences are set, it might crash WindowServer making it impossible for that user to log in (log in, Window Server starts up, crashes, back to login screen). I had to go in via another user, clean out the affected user's prerefences, after which logging in was possible again (though all preferences were lost)
- Booting a system with a USB SSD attached (SanDisk) via USB ends up in a situation that the whole disk isn't seen (missing from System Info) until you physically disconnect/reconnect the drive. Two Thunderbolt drives connect fine and so does a USB RAID
- Attached wired keyboards/trackpad (all Apple) unable to wake a system from deep sleep, you need to physically disconnect/reconnect them to get them recognised
- A monitor as second monitor on an iMac. When the monitor is turned off, the main screen works but input (trackpad, keyboard) gets stuck for a half-second or so all the time.
- If you use software that allows connections from the outside and you use the Application Firewall (ALF) to protect your system, at some point using ALF meant that a certain service would stop working after a few hours because the kernel had stopped passing connections on to the software. Stopping and starting the software made it work again for a few hours. This software ran fine under Mojave and several earlier versions. It seemed that the kernel ran out of resources and that stopping and starting the software freed them. I had to stop using the firewall as a result.
- Services that are started by hand work fine, but when started via launchd are unable to reach.
- And the latest: under 12.5.1 the system suddenly freezes for all connection requests (e.g. you cannot ssh in to the system, or use ARD, etc. Nothing that requires TCP/IP it seems. Ping works, but no TCP/IP port can be reached. Most of the time, this will resolve itself after a while as if the kernel gets 'stuck' and at some point gets 'unstuck', but sometimes it doesn't and you have to hope you are logged out and can click the restart button or you have to do hard reboot. The last time an unstuck happened after an hour or so.
I have my suspicions about what may be in play here:
Apple has always been that weird combination of 'insane level of attention to detail' in one place and 'insane level of neglect' elsewhere. But I have to conclude that now that Monterey is at version 12.5.1 it still is buggy, fragile, unreliable. It is a P.o.J. and I am very sorry that after more than 20 years of Apple use I have to give up on ever having something as robust as it was years ago. And the history of recent versions have been that they have become worse and worse in terms of reliability over the years.
- Apple not spending as much energy on x86 as it does on M1 (which pisses me off as I spent thousands on all these machines)
- Apple working hard on adding security (e.g. the kernel being able to merge a read-only and writable volume into one file system, very neat, and a lot that is now connected to software being signed) but not doing a very good job at writing correct code that can handle all the different situations ('happy flow code')
- The 'unstuck' behaviour of 12.5.1 really feels like Apple has put in some stopgap measure to make sure that if the system gets stuck there is some sort of low level 'reset'. Or, Apple knows this is unreliable, but has implemented some sort of garbage collection that once in a while cleans stuff up so it starts working again
I have started to investigate moving parts of my (until now 100% Apple) landscape to another OS because the level of reliability has become so low that I have lost my confidence that it will be reliable any time soon.
Unless there is a software or hardware item that only works with Windows in a non vm or bootcamp scenario, there is no reason not to have Mac as a desktop. I find it amusing that years ago, there was a push to get rid of Macs in many corp environments. Today, lots of people use iPhone, iPad and Mac laptops in a business environment.don’t do it. Already did this many times.
Conclusion: apple dominates laptops, unless you are a gamer(or rather, your game isn’t supported/streamable). If you do anything else BESIDES gaming, the MacBook is amazing.
All my work issued laptops can’t get passed 4 hours untethered. And windows is slow while on battery. Plus they all get VERY hot. Lid/standby always is slow.
I’m just not as productive on a windows laptop.
I literally just did an entire day’s work on my bed, no overheating, no anxiety about fan breathing space, no slowdowns, and long long battery life. Mac makes it easy.
But for desktop, stick to windows
Snow Leopard. Best version ever.Many people say this. It's like M2 'SSD gate', where it's been argued barely anyone will notice because who on earth buys an MBA for serious work. And while there is room for this point of view, it kind of implies your average buyer is someone spending £1249 upwards on a computer for banal content consumption and incredibly light tasks. Zero evidence on my part, but I really can't believe that's true. That's what £300 Lenovos are for. People expect computers costing a grand or more to be capable of some pretty serious heavy lifting, and expect them to come with a solid OS which doesn't trip over itself.
It's all about the 'premium price, premium product' image which Apple once prided itself on.
Now they're more interested in pairing-up with Kardashians to sell skin-coloured earphones, and we wonder why MacOS is going to hell on a handcart.
EDIT: I miss Snow Leopard
I thought that was correct behaviour? MacOS renders a 4K display as 5K internally, then scales it to 4K to allow pixel doubling/hidpi/whatever you want to call it.
- A 4K LG monitor that isn't recognized as 4K but as 5K. Notable: that same monitor is recognised fine on the only M1 Mac over here. Note also: I have 5 different Macs in this household, this clearly is not a hardware problem if all the Monterey x86 Macs do not recognise the monitor correctly, but the same hardware before the upgrade did, the only x86 Mac still running Big Sur does, and the M1 Mac running Monterey does.
Apple has always been that weird combination of 'insane level of attention to detail' in one place and 'insane level of neglect' elsewhere.