3 ms·
The problem with Windows is that there isn't a lot of API for very important system tasks. Instead, everything is held together by convention -- a DLL copied t
by wvenable 16y ago
The problem with Windows is that there isn't a lot of API for very important system tasks. Instead, everything is held together by convention -- a DLL copied to the system directory, a registry key, shortcut files, etc. This has made it much harder for Microsoft to adjust Windows to better handle a much more user-hostile world. It has also made the software more brittle because they simply aren't forced to follow the convention.
For example, installing and uninstalling software is broken in Windows because there's no accounting by the operating system as to what was changed -- if an uninstaller is broken the user is pretty much stuck. If applications were forced to install themselves completely using a system API, then Windows could track the changes and simply undo them itself. This could be pretty low-level (it doesn't have to be MSI, for example) but if you want to write a file into the /Programs/ folder, you need to use an API that does just that. And if Microsoft decides to rename that folder again you are guaranteed that every application will continue to work.
This can be equally true of setting file associations, adding desktop/startmenu icons, the notification area, and auto updators. Applications have been allowed to basically spam your computer with icons and background tasks. This doesn't necessarily need to be sandboxed out of existence but instead held behind an API that empowers the user. Mobile operating systems already do much of this by asking you at install/runtime what access an application should have and then providing a system control panel for adjusting this access after the fact. Wouldn't it be great if there was a control panel that listed every background task started by Windows with the program it belongs to, a description, and the option to turn it off?
- djacobs 16y agoThat is certainly one problem Windows has. It's also not really orthogonal (I'm looking at you, registry) and doesn't strive for simplicity or elegance like Unix/Linux tend to do. (Why the user folder is so ambiguous and mysterious before Windows 7 is beyond me.) If Eric Raymond is to be believed, another problem is that it has no unifying concept, a la Unix's "everything is a file" or Apple's "make the GUI simple and focused".
- wvenable 16y agoIf they had provided APIs for every function that is part of the registry, they could changed the implementation at will. Instead, the registry is just another file system with all the same problems. Unix also suffers from the same problem of convention over API. They do have a better convention and "everything is a file" is sort of an API onto itself but the concept is pretty much gone once you reach the level of Windowing System.
- eru 16y agoPlan9 resurrected the idea of files for windowing systems. (http://plan9.bell-labs.com/plan9/about.html http://plan9.bell-labs.com/plan9/about.html)
- gaius 16y ago"Everything is an OLE server" is the closest Microsoft concept. And it is too - files on NTFS filesystems are a lot more than just files, only (nearly) no-one uses all the fancy stuff, and it's not really exposed through Explorer or CMD. You don't really need file extensions, for example, but everyone is so used to them. The Registry arguably is no more or less sensible than /etc full of cryptically named config files and executable scripts, all in slightly different formats...
- agazso 16y agoThe Registry is a pseudo file system inside the file system. It is one of the reasons that Windows is so much harder to backup and restore than Unix is, because parts of it contain system state and other parts contain configuration and the whole is mixed into one big mess. On the other hand, text files are universal.
- gaius 16y agoOK, but it's not as simple as that. Man fstab-sync, for example, and you'll see that your config files can be mysteriously rewritten. Or resolv.conf being dynamically modified by DHCP. /etc is more complicated than just a directory full of text files.
- silvestrov 16y agoThis is not completely unlike the process model that Mac OS 7 had. Extensions could easily screw up the system, applications could write all over the filesystem and even damage the "System" resource file. All applications could modify all of memory. OS X added process protection and fixed most file permissions and /System is almost read-only (some 3rd part still install stuff there). The major tool was Carbon: provide all the functionality as system calls instead of modifying lowlevel memory directly. Carbon was sourcecode backwards compatible, so you could easily modify your app and still have the same binary running on old Mac OS versions, and run on OS X at the same time. Mac OS would have had Carbon-style protection sooner if Apple had not dreamed of Copland as the golden bullet as the future OS. Microsoft needs to create a "Carbon" for installing and updating apps.
- nuclear_eclipse 16y ago> Wouldn't it be great if there was a control panel that listed every background task started by Windows with the program it belongs to, a description, and the option to turn it off? So.... `msconfig`? Ok, maybe it doesn't have all the descriptions, but it still lists all the registered services and allows you to disable them.
- wvenable 16y agoI've never seen anyone but a power user use msconfig and even I have to google the file names to discover what some of the stuff does. I'm thinking of something considerably more user friendly.