Though most of the low-level code was retained, a lot of code at the API level and above was effectively ripped and replaced, either because of dependencies on other parts of the platform that were also in flux (e.g., .NET - Explorer and Sidebar changed at least in part due to the need to cut such dependencies) or because feedback drove significant changes in the current architecture (e.g., WinFX, WinFS, Object Spaces, "Castle"). There were also low-level platform components not present in 2003 AFAIR (e.g., "Longhorn" builds of that era still used XPDDM rather than WDDM), and I don't think the protected process architecture was in place. Other technologies have also been added such as ASLR and Workflow.
You do realize that Microsoft has a lot of developers.... it's not as if the Vista developers were told to stop progress on Vista and concentrate on XP SP2 so you could get a firewall (and finally after how many years... a tiny little update to IE).
You're exaggerating way too much by characterizing XP SP2 as just a Firewall/IE update, and XP shipped with a firewall at RTM. Most people just didn't bother to turn it on, which is why it is on by default in SP2. There were changes to the security model in various areas, DEP was introduced, and system components were recompiled using new compiler technologies to help mitigate exploitation of common code defects.
Microsoft stopped all development for two months to provide security training and code review. After development resumed, many developers were indeed pulled off "Longhorn" to work on XP SP2.
This post was edited by n4cer on Thursday, October 19, 2006 at 12:12.
|