The backwards compatibility remains a huge feature of DOS and Windows.
Sure some new games are cross-platform and work in Linux and Mac, but for anyone who's been gaming for awhile, most of your favorites are PC, and a lot of 'em will still work. A few of the ones that used oddball custom memory management near the end of the DOS era won't work on a modern system. And some that used custom VB controls in the Win-95 era. But a surprising number overall still do.
One that amuses me is SST.[1] Written in the late-60s to early 70s on a mainframe, then ported to PC in the early 90s, still works just fine in Windows 10 (last updated in 2019). Still has a teletype terminal style interface, but also it still just works. And sure, a lot of that was due to the porting done in the 90s, but a lot is also just due to the basic stability of the platform.
That's a game my dad might've played in school, and my grandson could play now.
I wonder how much software written today will still 'just work' in 30+ years? Sure, we can use virtual machines and emulators and such, but without that, will anything written today still 'just work' the way old software does? So much now is constant churn with monthly/weekly/daily updates and dependencies and everything - constant maintenance to keep it running. So many network dependencies even for things that don't need them. I'd say most of us aren't really building software to last.
And if nothing is built to last, that great value of backward compatibility and longevity is lost. Which is kinda sad.
[1] https://almy.us/sst.html