Quote: Originally Posted by jimbo45
Windows on the other hand was designed as a GUI from the start which makes it rather difficult to change almost anything without re-writing the whole system.
There probably is a lot in Windows that people could do without in some cases but since in any case the GUI is 100% linked with the OS it will need a major re-fit to slim it down a lot.
Yes and No. When Dave Cutler was brought in to start designing NT as the new UNIX killer for MS, the original plan and the original builds, were for it to be commandline only. But, because it would need to run OS/2 apps (MS and IBM were working together on OS/2 at the time), Cutler wanted basically a VM to startup when Presentation Manager (OS/2) programs were started.
When Windows 3.0 took off, Gates realized that he had a winner and he forced Cutler to change ways. MS bailed on IBM and decided to have NT become the new flagship 32-bit OS, capable of server and workstation ops. The Win32 API was quickly developed, from the Win16 API (bugs and all). This then had to be bolted onto the kernel that Cutler had already started, and that process was much harder than expected.
Unfortunately, Win64 continues the string of quick ports from Win16 to Win32. MS is between a rock and a hard place. A new GUI API is needed to remove so much of the kruft that has built-up over the decades, but the amount of effort involved in doing this, and the number of apps that would be broken by this is unacceptable to them.
They have treid to mitigate this with various frameworks, .Net, WPF, etc,, but all of these still require interaction with Win32/Win64.
Peter Bright, an admin on ArsTechnica, has written some really good articles on where MS has dropped the ball. He is a very knowledgable programmer who provides some pretty good insight. He is very plain spoken, so if you are easily offended, you might want to avoid direct contact
, but he certainly knows his stuff.