• Moving to a packaged based update system for Windows

    Home » Forums » Outside the box » Rumors and what-ifs » Moving to a packaged based update system for Windows

    Author
    Topic
    #227531

    You know, I’ve been thinking of how could Microsoft improve the update process lately. I think that moving the entire OS to use packages to deliver updates (like how Linux does). Since NT (in theory) is made to be a customized for each SKU while still using the same essential code, packaging each component to separate packages has a nice balance: you can still download the packages that are known to work fine all the while the annoyance from downloading 100+ packages is almost gone since you only download the latest version of the component, rather than download 6 (or more) just to do the same thing. Combine it with delta patches, Active Hours and restarting non-essential components (and releasing hotfixes a lot faster, as long as it doesn’t require a computer restart) and you have a pretty robust update system.

    So, if it is pretty good, then why Microsoft can’t implement it? Well… trying to implement it will take a significant work to implement it in the kernel level. And it will break programs in the process. Plus, the Update Deployment Servers for businesses will need an overhaul as well. Maybe when a new kernel is being developed?

    Viewing 0 reply threads
    Author
    Replies
    • #227593

      That might be a good way for makers of operating systems to keep their systems and associate software up to date. However, MS is not even interested, or perhaps as hinted elsewhere, even capable of updating and patching the current version of Windows, so I don’t see these ideas getting much results as far as Windows goes.

      One thing to think about, perhaps, is having an enforceable set of standards for the operating systems being distributed, at least, to more than certain number of licensees, so the current slow train wreck of world-wide proportions never happens again. An example of this is the POSIX IEEE standards later adopted by both ISO and IEC international organizations of standards to ensure the intercompatibility of operating systems, primarily the variants of the UNIX OS and its derivatives LINUX, BSD, FreeBSD, AIX, etc.

      That means that an OS not endorsed by those international standards’ organizations with their seal of approval will be clearly and visibly not so blessed, and people can install and use them if they like to live dangerously, but otherwise not complain too much, in court at least, about it. In other words: “As Is” no longer will be the standard, particularly for commercial (and often expensive) OS. And flaws in them introduced after the seal of approval has been granted (e.g., with poisonous patches) could be looked into by specialized lawyers to find out and prove in court, if turns out to be the case, that the systems have been advertised as in compliance with those standards when, in fact they were not and this was known by their makers (false premises), or should have been if they had bother to check before distributing them to the users, their customers (negligence).

      By the above I am not suggested that a one-of-a-kind OS such as Windows should be subject to POSIX compliance, but some set of standards should be found and adopted for such OS, so as not stifle innovation.

      Much as, with light bulbs, there are standards of manufacturing meant to ensure people do not get electrocuted when handling them with reasonable care, or have them implode in their faces or spill mercury all over the place.

      Maybe something worth thinking about?

      • #227612

        AceOfAces: This entry was mine: forgot to login, coming directly from the invitational email…

        Best of luck with this thread you have started on such an interesting topic. I hope you get some interesting answers.

        Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

        MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
        Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
        macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

    Viewing 0 reply threads
    Reply To: Moving to a packaged based update system for Windows

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: