After mulling over it for close to 14 years, it seems Microsoft is finally ready to kill off the Windows Control Panel soon. An official confirmation has been posted on its website.
On the flip side, this is what makes Windows generally very good at backwards compatibility. They do update the codebase for stuff, but still generally very backwards compatible with software and games designed to run on previous versions of Windows.
Yeah, that makes sense. If it’s starting to bite them in the butt, though, maybe they should start relegating that stuff to emulation, if they can write a good enough emulator.
I don’t know when. Maybe it’s already gone by, maybe it’s in the future. But there’s probably a point in time when all of that backward compatibility stops being worth it.
While I haven’t diven into their codebase, that kind of thing tends to severely limit what developers can do to improve the product, slow them down, etc.
Be it new features, deeper UX improvements, performance optimizations… Basically anything you want to do with your progress, generally speaking, it’s going to get harder the more legacy stuff you need to deal with.
Oh I see. Well if it has exactly the same API, if that API also has weird legacy stuff built in that hinder developers, then maybe not, but overall that does sound very similar, yes!
My god, the amount of legacy crap in Windows.
They ought to just start over at some point.
We need Windows NNT - New New Technology
How about Windows NEW ALL (in reference to Tantacrul)?
New all, everybody!
On the flip side, this is what makes Windows generally very good at backwards compatibility. They do update the codebase for stuff, but still generally very backwards compatible with software and games designed to run on previous versions of Windows.
Fun Fact: Backwards compatibility is the reason you can’t name a file or folder CON.
Yeah, that makes sense. If it’s starting to bite them in the butt, though, maybe they should start relegating that stuff to emulation, if they can write a good enough emulator.
I don’t know when. Maybe it’s already gone by, maybe it’s in the future. But there’s probably a point in time when all of that backward compatibility stops being worth it.
Is that a real concern?
While I haven’t diven into their codebase, that kind of thing tends to severely limit what developers can do to improve the product, slow them down, etc.
Be it new features, deeper UX improvements, performance optimizations… Basically anything you want to do with your progress, generally speaking, it’s going to get harder the more legacy stuff you need to deal with.
Isn’t that what wine is ?
I don’t understand
Wine (wine is not (an) emulator) is a reimplementation of the windows api set. It’s literally starting windows again from scratch.
Oh I see. Well if it has exactly the same API, if that API also has weird legacy stuff built in that hinder developers, then maybe not, but overall that does sound very similar, yes!