Re: Company bloat/inertia?
I don't think it's because of Company bloat/inertia; rather, I think it's symptomatic of a flawed design philosphy.
For example, consider the problem with launching W32 apps from the start menu in this latest build, and the suggested work-around: what on earth are they doing with the program launch process to make it so fragile?
It's the regular occurence of slightly weird problems like this that leads me to the conclusion that the Windows OS is designed, by intent, to incoporate an extremely high degree of very deep integration, not withstanding recent moves towards greater modularity. However, the problem with very deep integration in a very complex system is that a relatively insignificant problem, in an insignificant subsystem, can impact other more important subsystems, despite there being little logical interlocking and/or interdependency between them.
It's difficult not to make comparisons between Windows and Linux in this repect; whilst both systems rely upon a monolithic (modular) kernel, Linux doesn't try to incorporate the deep integration* that appears to be such a major feature of Windows, and certainly, in my experience, doesn't seem to suffer from the same sort of rather weird problems.
For most users, the major difference between the various versions of Windows is the interface, probably followed by any new services/features, and then followed by boot/load times. I see very little info regarding changes in the kernel or infrastructure services though, which is where any work is actually done.
* yeah - systemd bait.