3 ms·
What I don’t understand is why can’t they just simply replace the binaries and reboot. I am sure 99.9% of pc owner must not apply hotfixes or updates selectivel
by cm2187 8y ago
What I don’t understand is why can’t they just simply replace the binaries and reboot. I am sure 99.9% of pc owner must not apply hotfixes or updates selectively. They could make those fast, and keep the slow process for the 0.1% who need this level of engineering.
- ocdtrekkie 8y agoLinux is a file system based OS, that works. Windows is a database based OS (the registry), just replacing the files often does not work.
- pbhjpbhj 8y agoCan you expand on that, it doesn't make sense; are you saying databases inherently take a helluva lot longer than file systems to update ... file systems are databases ...
- acdha 8y agoThe correct way to describe it is that POSIX filesystems allow you to replace open files but Windows does not, so they had to queue updates until the boot process guarantees that nothing is using them. The POSIX approach makes it easy to install updates without rebooting but opens you to weird failures if a process loads things during an update and gets the new library A and old library Z. This is generally a much easier problem to handle.
- anticensor 8y agoCorrect way to solve that would be adding a new privileged Windows API call which ignores file locks and lies to other applications.
- acdha 8y agoIt’s been awhile but I thought that would complicate the way they load DLLs, not to mention the potential impact on legacy code which was doing something unsafe but would no doubt be spun as Microsoft unfairly breaking someone’s security kludge or dubious extension. Not something which can’t be handled but increasing the cost/risk perception. The big thing, though, is that they had a lost decade or so where the stack-ranking system heavily favored new features over improving existing code. Unless this was such a problem that it became a senior management priority I doubt anyone was jumping at touching it.
- pjc50 8y agoIronically Gnome replicates the registry for the same purpose of holding configuration. You can't just replace the files and reboot because you can't write to files while they're open, especially executables; so what happens is a huge pile of files get queued for swapping over at reboot. I think the main reason Windows Update takes so long is that it has its own database, WSUS, which degrades badly as it fills up.
- nikanj 8y agoEither they're so dumb that they never thought of this, or there's a complex and multi-faceted reason for the way updates are delivered. Considering that Microsoft still does have a lot of really bright engineers, I'm leaning towards the latter.
- cm2187 8y agoI don't know. There are lots of weird design decisions in Windows. We shouldn't underestimate inertia in large organisations.