Comment

Windows’ bloat isn’t because they have to maintain backwards compatibility. It’s because they keep adding more shit, and the shit they add isn’t exactly hyper optimized.

Well, it’s both of those. There is plenty of bloat due to a necessity to maintain backwards compatibility. I’m well aware of the extra shit they add, but that’s not what I’m asking about.

Apple’s MacOS transition is driven by the hardware change. The next MacOS will not support Intel machines, so I would imagine those aspects of compatibility will be removed.

The question was related to an equivalent aspect in Windows: since Windows 11 requires certain hardware, why doesn’t Microsoft treat Windows in a similar vein?

source

Sort:hotnew top

fuckwit_mcbumcrumble@lemmy.dbzer0.com ⁨1⁩ ⁨week⁩ ago
I mean in terms of disk space sure it takes up a good bit. From what I can tell winsxs takes about 10 gigs of space. But the actual wow64 subsytem only takes a 1-2 hundred MBs of RAM which is nothing for giving you that much backwards compatibility.

Rosetta 2 is going away in the next Mac OS, but that’s not going to have a massive impact on anything. The biggest impact will be the installer will be half the size since it doesn’t need twice the executables. You can download an Intel or Arm specific installer of Mac OS and it’s already half the size.

why doesn’t Microsoft treat Windows in a similar vein?

Because then nobody would use Windows. People use windows because it runs all of the programs they love. If it didn’t people wouldn’t put up with their bullshit.

source
- Quicky@piefed.social ⁨1⁩ ⁨week⁩ ago
  
  Because then nobody would use Windows. People use windows because it runs all of the programs they love. If it didn’t people wouldn’t put up with their bullshit.
  
  The suggestion isn’t to completely destroy compatibility with modern windows applications. And besides which, those same wholesale direction changes didn’t result in a macOS exodus.
  
  source