[edit] 3.1 should have been windows for worgkroups 3.11
[edit] 3.1 should have been windows for worgkroups 3.11
- Big software vendors (Autodesk, Adobe, etc.) making it difficult for Microsoft to deprecate or evolve APIs and/or design approaches to the OS.
- Cybersecurity/IT security groups strongly discouraging anything new as potentially dangerous (which is not incorrect).
- Non-tech people generally not caring about desktop PCs anymore - phones have that crown now.
- Non-tech people caring much more about interface than the actual underpinnings that make things work.
Outside of the PC there's some innovation happening, at least with the OS itself and not user interfaces. Check out Fuschia sometime.
Sorta. It was real pain-in-the-ass to run 2000 as a regular (non-administrator) user. Assuming your software worked at all that way, as even Office 2000 had some issues. UAC was necessary.
UAC and the other magic on Vista/7 mollified that by a lot.
Microsoft introduced I/O Rings, more or less a 1:1 copy of io_uring, in Windows 21H1.
https://learn.microsoft.com/en-us/windows/win32/api/ioringap...
https://windows-internals.com/i-o-rings-when-one-i-o-operati...
https://windows-internals.com/ioring-vs-io_uring-a-compariso...
Windows 8/2012 R2 did introduce Registered I/O for WinSock which is very similar to I/O Rings and io_uring.
https://learn.microsoft.com/en-us/previous-versions/windows/...
Win11 does have something similar: https://learn.microsoft.com/en-us/windows/win32/api/ioringap...
IBM pioneered hardware virtualization for isolation on their System/370 mainframes with VM/370 in 1972.
VMWare ESX hypervisor brought virtualization to x86 servers (2001).
Xen hypervisor introduced open-source virtualization for x86 (2003).
By the time VBS showed up, the concepts were already several decades old.
VBS uses a hypervisor and hardware virtualization to isolate processes for security. These concepts trace back to systems like the IBM VM/370.
Conceptually it's essentially the same thing. The difference with VBS is the scope and purpose of what's being virtualized.
3d compositing, ssds, mega displays, massive multi core, all completely wasted.
You know what I should be able to do? Hot execute windows and Linux and Osx on the same desktop without containerization that leaves 3d as an afterthought or worse a never thought.
Also a big degradation is the whole "hidden" %appdata% folder that grows and grows in size with no tools to deal with it.
As for appdata... There's many faults to find in modern Windows changes, but I'm not willing to pin this on MS. Microsoft stuff tends to use %appdata% fairly sensibly, in most cases. On the other hand, the behavior of third-party developers has been really frustrating. What was initially intended as a universal storage location for some program data has become some kind of program container. Now, whenever you download some giant 300-500mb Electron app or whatever, you can be sure that it will force its entirety into appdata with no way to change the location. Every one of these developers has decided that their program is so valuable and Important that it's inconceivable that the user might want to install it on anything but the system drive. No, our program is unique and deserves nothing but the best!
Monopolies. They ruin markets. Destroy products. Reduce wages. Induce nostalgia.