This is simply how Apple does things. They provide software support for ~10 years and then they drop it.

Is it wrong? I’m not entirely sure. You can call that greedy, but take a few things into consideration. Firstly, Apple provides highly specialized software that runs extremely well and efficiently on their own hardware. Continuously providing support for old hardware while simultaneously maintaining the same level of performance is simply not feasible. I challenge any software developer to achieve a similar goal.

We are not talking about Linux here, where if you’re lucky, things work. Anyone’s that ever used macOS even once knows that things really work.

Now, I assume this window of time between a new hardware’s release and the software drop for that given piece of hardware will increase over time, given that new hardware released by Apple nowadays is incredibly performant, this would allow longer software support.

Frankly, my opinion is that 10 years of support is more than enough for anyone to consider renovating their hardware.

Recently, in the last XNU kernel release (corresponding to macOS 13/iOS 16) the 32-bit part of the kernel has been entirely removed, meaning that XNU won’t support any 32-bit device anymore. This is really exciting to me, as I see the technology moving forward, without getting stuck on prehistoric hardware support.

>"Anyone’s that ever used macOS even once knows that things really work."

I am not a regular Mac user but I was once asked by client to port my CI/CD related script so it can work for developers who use Macs. Script involved dealing with docker among other things. After dicking around for a while I've discovered deeply nested folder created by docker that was not supposed to exist after successful script completion. Do not remember all the details but this folder was a thorn. Short of sacrificing a virgin no matter what I tried I was not able remove it. Invoking search power of Google did not help either - plenty of recipes and suggestions and none worked. Finally after giving this Mac to system gurus and them dicking with it for a day I was told that they have failed so far it is no longer worth their time and they will reinstall the OS.

Macs have a bunch of weird quirks where simple things simply do not work. I got a new mbp for work recently, second to my main windows gaming machine with 34" ultra wide 1440p monitor.

And I've basically installed chrome, vscode, and a whole bunch of little packages to make basic hardware operate normally. There's an app to allow the track pad and mouse wheel scroll directions to be set differently. There's another to allow the mouse side buttons to work. It's a basic mouse. These are settings and compatibility issues that do not need to exist.

But the most annoying is that the monitor is a bit blurry on the M1. I use vscode for a few mins before I realise there's a fuzziness to it. And apparently this is a known issue, because macs only scale properly for 4k resolutions. So there's another app to make it think its 4k or something. Helps a bit but not that well, and it's a trial. It's maddening. How the hell is anyone supposed to know that Apple has just decided that they won't be compatible with an entire category of bloody monitors, of all things.

Macs only look good at a 110 or 220 pixel density.

34" ultra wide 1440p has a pixel density of about 110 ppi, and that should work just fine. You might need to use a different cable, though. You should look your monitor up on rtings.com and search for notes on Mac compatibility.

I have a MacBook Pro 14 that I use daily with a 34" ultra-wide 1440p gaming monitor, and I've never had a problem. I had a MacBook Pro 13 before the 14 that also worked without issue.

The problem is that macOS killed off subpixel anti aliasing, which is important to making text look good on 110ppi displays. So 220+ ppi displays are the only real option here.