3 ms·
> I don't know what parts of the control panel must remain for backwards compatibility (with what!?) Because programs and drivers can and did ship their own co
by mschuster91 5y ago
> I don't know what parts of the control panel must remain for backwards compatibility (with what!?)
Because programs and drivers can and did ship their own control panels, it's fairly easy (https://www.codeproject.com/Articles/29264/Control-Panel-Applets-for-everyone https://www.codeproject.com/Articles/29264/Control-Panel-App...). Java comes to my mind, as did some virus scanners, and drivers for all kinds of hardware - and the latter is the key why MS keeps the architecture in place, they take backwards compatibility extremely serious, to the extent you can (generally) use Windows 95-era games and other software on a Windows 10 machine!
The other part is that there is an utterly absurd amount of things that can be configured in Windows, with a lot of ways to do so: text-based configuration files on the disk (e.g. /etc/hosts), registry settings, group policies that are mapped to registry settings, classic control panel applets, new control panel applets, the whole mess that is the bootloader config... all of this needs serious effort to re-organize, for something that 99% of end-users won't ever touch.
And that explains why there is such a split: the stuff that end users regularly need (display resolution, wallpapers, audio, ...) is in the new crap look, and the stuff that even nerds rarely touch (user-wide environment variables) is in the old school CPL applets.