This is kinda how I feel about Windows these days. It’s interface, directory structure, shudder the registry, user specific apps (from MS Store or Winget), buttons being inserted into the menu bars on some apps, but not others, button sizes being different sizes, some parts still using the Metro interface. The whole thing either needs a re-write, or should be dropped and something new to replace it. Don’t even get me started on things like the eventvwr hanging for 20 seconds after it opens, event tracer API, their in-house abandonment of powershell modules once powershell was open sourced, Windows containers being a disaster, etc.
The problem is that so much critical infrastructure around the world relies on ancient Windows software. I’m pretty sure their backwards compatibility is one of the reasons there’s so much inconsistency in Windows, and every iteration seems to just add more bloat on top.
They hired the man behind systemd (controversial, I know, but he does have a vision). I hope they listen to him and/or he starts directing how they should do things from the ground-up.
There was a TCP/IP bug that shared it’s exploit on versions of windows from windows for workgroups 3.11 (which you ran from the DOS prompt by typing ‘win’) through to windows 7 (which was the new hotness at the time)
That’s a bug conserved from the very first Microsoft implementation of TCP/IP through to the state of the art at the time
People were surprised at the time that it wasn’t a windows NT bug
That’s surprising, as I think the first Windows TCP/IP stack was ported over from BSD by Spider Systems (pretty sure that’s why it still has things like “/etc/hosts” - albeit under System32). Wonder if the bug was in BSD and never backported (cross ported?).
This is kinda how I feel about Windows these days. It’s interface, directory structure, shudder the registry, user specific apps (from MS Store or Winget), buttons being inserted into the menu bars on some apps, but not others, button sizes being different sizes, some parts still using the Metro interface. The whole thing either needs a re-write, or should be dropped and something new to replace it. Don’t even get me started on things like the eventvwr hanging for 20 seconds after it opens, event tracer API, their in-house abandonment of powershell modules once powershell was open sourced, Windows containers being a disaster, etc.
The problem is that so much critical infrastructure around the world relies on ancient Windows software. I’m pretty sure their backwards compatibility is one of the reasons there’s so much inconsistency in Windows, and every iteration seems to just add more bloat on top.
They hired the man behind systemd (controversial, I know, but he does have a vision). I hope they listen to him and/or he starts directing how they should do things from the ground-up.
There was a TCP/IP bug that shared it’s exploit on versions of windows from windows for workgroups 3.11 (which you ran from the DOS prompt by typing ‘win’) through to windows 7 (which was the new hotness at the time)
That’s a bug conserved from the very first Microsoft implementation of TCP/IP through to the state of the art at the time
People were surprised at the time that it wasn’t a windows NT bug
That’s surprising, as I think the first Windows TCP/IP stack was ported over from BSD by Spider Systems (pretty sure that’s why it still has things like “/etc/hosts” - albeit under System32). Wonder if the bug was in BSD and never backported (cross ported?).