> This ridiculous complexity and scale highlight why Microsoft has historically struggled to deliver reliable feature updates for Windows 10, forcing them to dr

> This ridiculous complexity and scale highlight why Microsoft has historically struggled to deliver reliable feature updates for Windows 10, forcing them to drop “Windows as a Service”, moving to a more manageable yearly update schedule. The author seems to have a distinct lack of understanding of windows codebase. They didn’t move away from windows as a service because of code complexity, they did it because businesses didn’t and don’t want a rapid release cycle for desktop, they want stability. And NOBODY wanted massive UI changes without a very clear version difference so they could move to the new UI when they were ready. Windows as a service was a bad idea they properly course corrected on. Furthermore, most of the code he’s referring to is up the stack and would presumably need to be ported to Linux unless they’re going to abandon all of their enterprise users and apps (they won’t). MinWin was only 25MB after all (yes I realize that isn’t a complete OS but it gives you an idea of how much space all the “other stuff” is taking up).