The other flip side is 25-30 year old bits of UI cruft in windows, along with the associated security flaws in said 25-30 year old components.
First off, who cares about old iconography? Like, fine, it's an eyesore to you. Does it still work? Does it otherwise need changing? Also, UI that hasn't been updated in 30 years doesn't necessarily equate to 30 year old security flaws.
Plus a company that clearly has no direction - they've changed the task bar UI in Windows 11 3 times in the past 5 months, and the end result has not been an improvement unless you like providing revenue to Bing.
Microsoft uses telemetry to get feedback for things like Windows and Microsoft 365 so that if people don't like how it looks or runs, they can change course in these feature drops or in versioned Feature Updates before the OS becomes the second coming of Windows 8. They're changing course so many times because people complained and they listened. Would be nice if Apple did that for a change. Maybe we wouldn't be stuck with the nightmare that is System Settings.
Not much point in giving examples if you're just going to say, effectively, "sure, but that doesn't bother me".
You made an assertion that Microsoft is being held back by backwards compatibility. I challenged that and asked you how so. You came up with nothing.
Taking forever to sunset things does not constitute being held back, especially if the pieces that they are taking a while to sunset are not actually holding the platform back (as is true of both Control Panel and Internet Explorer).
I didn't say "it doesn't bother me". I asked you for an example and you didn't deliver.
I'm quite happy with the consumer choice between "move fast and break things" and long-term stability, but they both have pros and cons.
The biggest backward-compatibility issue with Windows, historically, were the security problems from the Windows XP era onwards, caused by everybody needing to run as "admin" in order not to break Win95 era code - and the knock-on effect of "training" users to ignore security warnings.
Windows 95 is about to have its 28th birthday. Windows XP is about to have its 22nd birthday. Incidentally, the jump from Windows 95, 98, 98 Second Edition, and Millennium Edition (all MS-DOS based operating systems) to Windows XP (a Windows NT based system) was about as radical for the platform as Mac OS 9 to Mac OS X. Steve Balmer and Bill Gates were asshats back then and didn't manage that transition terribly well. Again, you are citing a 22 year old example. Go back to when Windows 95 first came out, and you'll see Apple similarly making missteps that nearly led them to bankruptcy.
C.f. Apple who managed to completely switch from Classic MacOS to OS X (a completely different OS) within a few years and then make sure that the Classic "emulator" was dumped before the next big transition rolled around...
First off, Classic wasn't dumped before the Intel switch. Classic was dumped when Mac OS X Leopard came out; the first and only OS to simultaneously release for both PowerPC and Intel. Secondly, Apple BOUGHT NexT and with it a bunch of industry-leading talent that made the whole thing possible. You act as though Apple pulled this off in a vacuum. They didn't.
Microsoft are currently on their 2nd attempt at Windows on ARM (and non-x86 in general) and a couple of years in it really doesn't seem to be making waves with the main complaint being lack of software.
The first attempt was aimed at competing with the iPad. Not with the Mac. That's a seriously key distinction. The idea wasn't baked in the oven long enough because it entailed horrible UI without the option to not have to use it (at least you are not forced to use LaunchPad if you don't want to).
The only reason why Microsoft has a lack of software problem is that they are not forcing developers to produce ARM64 binaries. It's optional. VERY similarly, I still have a fair amount of software that is still Intel-only. Moreso during this architecture transition than the PowerPC-to-Intel transition, developers are slow to update their apps to fully support Apple Silicon. Why? They don't have to. Rosetta 2 performance for most apps is still better than a native Intel Mac. And Apple hasn't announced a date in which Rosetta 2 will be deprecated. There is no incentive for anyone to update their apps if they don't want to. Sure, Adobe, Microsoft, and other similarly larger Mac software vendors are doing it. But independent software developers? Devs that don't stand to make money on updating an app they made for Intel Macs, let alone those that probably weren't pleased with having to suddenly update their apps to be 64-bit Intel just one year prior?
I'm not going to tell you that Microsoft is better when getting ARM64 Windows apps out there. But I will tell you that it's not great for both of them and for the same reason; for the time being, no one is forcing anyone to put out ARM64 binaries under the threat of discontinuation of compatibility with the platform as it stands today.
The most enthusiastic adopters of Win11 on ARM seem to be Mac users (I'd love to see the stats on how many Surface X computers there out there vs. how many people have activated Windows for ARM on a VM on their Mac...).
Lack of selection will do that. That's a hardware problem more than anything. Apple Silicon is a highly optimized SoC platform for the OS it is intended to run. None of the other SoC platforms are purpose built like that. All that being said, I'm pretty sure there are now twice as many ARM64 Windows systems available than there were in 2020 when Apple first announced the Apple Silicon transition.
It really shouldn't be a problem for "modern" Windows software developed with .NET/CLR and compiled to bytecode but here we are...
I can't speak to that since I'm not a developer for either platform. However, my guess is that you aren't either because I'm sure there's a ton more to it than that.
Meanwhile, Apple have almost completed their 3rd successful ISA transition (I'm not counting 6502 to 68k) and in each case the new system has hit the ground running, with most major software usable (if only via Rosetta 2/Rosetta/68k emulator).
(a) Apple hasn't completed this one yet. I don't doubt they will. But they are STILL selling Intel hardware and, at nearly the three year mark since announcement, there is a much smaller percentage of macOS software that is Apple Silicon native than there was natively on Intel in March 2008. Working emulator to cover currently non-ported software doesn't mean anything if Apple is subject to pull the emulator whenever they feel like it.
Technologies like Rosetta are much easier to pull off if all they are doing is translating code that is otherwise written for the current OS, and not having to provide loads of legacy libraries/frameworks or translate between 32 and 64 bit.
There's one theory and one fact that you can propose about this. They are not mutually exclusive. The theory is that Rosetta 2 was never going to be able to translate 32-bit x86 into 64-bit ARM. The fact is that Apple Silicon hardware that is A11 and newer is completely devoid of 32-bit instruction sets.
That being said, there was nothing stopping Apple from still shipping Rosetta 2 as it is and having it work exactly as it does while not dropping 32-bit Intel app support from the Intel releases of macOS. Nothing, that is, except for the massive damper that would put on Apple Silicon in the eyes of consumers. There isn't that much legacy cruft in macOS Mojave that was suddenly gone in macOS Catalina. And, by in large, Mojave is the smoother and more stable of the two OSes anyway. Supporting 32-bit code wasn't holding the OS back. It was preventing Apple from having Rosetta 2 be a failure in the eyes of customers instead of the success we all see it as now.
Also, "legacy" code support in OS doesn't maintain itself for free - esp. in the modern era where potential security exploits are continuously turning up in old libraries.
I honestly am unsure of what you mean here. Most software that can run in Windows 7, an unsupported OS, can also run in Windows 10 and Windows 11, supported OSes. Supported OSes get patches to plug up those exploits in whatever old libraries are present. Problem solved. Furthermore, Windows 11's more stringent system requirements have eliminated at least 60% of all Windows vulnerabilities. Hell, Windows 10 compartmentalizing the OS's components such that an attack on one part of it doesn't affect the others was pretty damn revolutionary. As someone who lives and breathes IT and cares greatly about remedying security vulnerabilities in endpoints, I think you might not know as much about this stuff as you think you do.
Microsoft has a huge number of corporate customers willing to pay for extended support. MS didn't keep rolling out security updates for Win7 until early 2023 out of community spirit - they charged for them.
Yes, Extended Support Updates solely for seriously large enterprises with software they were not ready to transition from. I was there for that. The number of businesses that needed to use these updates wasn't that large. Most moved to Windows 10 just fine. I worked at least four different Windows 7 to 10 migrations. You had some people not on top of things. And you had some people who absolutely needed to use esoteric software the likes of which would never exist on the Mac and that couldn't smoothly run in Windows 10. Rare cases, but they existed.
Apple's total MacOS user-base is still a lot smaller than Windows' and the lion's share of that is in end-user laptops and single-user desktops that get replaced every 4-5 years anyway. I doubt there would be many takers for a paid extended support program.
The paid extended support programs covered supporting Windows 7 for years 11 through 13 of its existence on this planet. Apple cuts things off after 3 years. The only people holding onto 11 year old hardware are 2010-2012 Mac Pro users. Otherwise Apple doesn't sell to people whose needs are THAT mission critical such that their drastic annual OSes are not an option.
I wouldn't bet the farm on Windows being in the same position in the future (the whole industry is gradually shifting towards cloud servers running JIT-compiled scripting languages, and the likes of MS are going to make their money selling cloud services, not traditional operating systems & support contracts).
There will always be users computing on endpoints. Not as many are buying desktops today as they were 20 years ago. Even not as many are buying laptops as they were 20 years ago. Most do their computing on their smartphone.
Microsoft will still exist. Windows will still exist. Windows will still lead the market because they can be depended on in situations where macOS cannot. And Windows will still lead the market because IT management of Windows isn't as hard to grasp as IT management of macOS. Just because iPads and Chromebooks have joined the fray doesn't change that.
. The "safe" option is probably Linux and open source, which might not run 20 year-old binaries but will compile 50-year-old code which, if it is open source, someone will probably have done for you.
You haven't used Linux much either, I see. There's never a guarantee that anyone has compiled any open source thing for you unless it's from a big company (i.e. Canonical, Google, Mozilla, etc.). Linux is safe if you know what you're doing.
Most manufacturers got rid of slot-drives because they were gaping holes letting dirt inside the computer. And they broke constantly, as the component the user bashed on the most, and were therefore a warranty pestilence.
They only got rid of them for one reason; they could.
I'll bite: when's the last time the MacOS had a security flaw that wasn't related to either Safari or any of Apple's other in-house app software?
Happens damn near all the time! This last zero day was Safari related. That much I'll grant you. Happened A BUNCH during Monterey's reign.
(I tell all my clients: "Never use Safari, for the same reason you didn't use Internet Explorer on a Windows machines.")
You can't get rid of it. Even if it's not your default, it's a bad idea never to patch it.
I don't start using an OS until Apple is finally done meddling with it, and I use old firefox clone browsers running ancient extensions, and am connected to the internet 24hr/day with MRT yanked out by the tonsils.
I'm not going to tell you how to live your life. But I will tell you that if you are an IT consultant and you are telling people to wait until an OS no longer gets security updates to move to it, then you REALLY shouldn't be in this line of work.