One thing that is a problem is that web pages get bigger and bigger and more resource intense. I doubt my 2011 air could handle a modern day web page with videos and a bunch of css transforms like on the apple site.
I believe Apple is pretty good about keeping people on the latest versions of their software, but it wouldn't surprise me if there were a few stragglers or people using EOL devices that are stranded on an older build. I can definitely believe that it's a PITA supporting them, though. Working around MacOS shenanigans is the most frustrating part of my job too.
> One thing that is a problem is that web pages get bigger and bigger and more resource intense.
Eh... I'm not sure if I agree with that sentiment. In the early 2000s there were also people saying "desktop apps are going to get bigger and more resource-intensive", but that never really happened. In fact, the Java runtimes people used in that era were usually heavier than modern applications today, or evestn Electron-bundled programs. IMO, the web has been resource-intensive ever since Javascript became the lingua franca. Nowadays, I think we're making progress to reduce the resources used on websites. Things like WASM and lighter JS frameworks are going to make all the difference here. In fact, I can even see ourselves in another Web2 golden age in a few years. I personally don't think the SAAS landscape is long for this earth, and once it fades away, there will be less incentive to make bloated, broken applications and more of a focus on refining user experience and performance.
I hear people say that today, but how is it going to feel in 2025, when you try loading up MacOS 16 on it? Given the trend of Apple's development, I don't think 8 gigs is going to be sufficient for most people going forward. That's basically iPad-tier memory constraints on a desktop-class operating system.