After reading Alex Barrett’s post Microsoft being Microsoft, I was curious what our virtualization experts thought of the whole ordeal. Here’s what they said.
Microsoft has a long history of delaying, and then delaying again their products. One could hold out hope that this is to keep the products in a controlled test environment long enough to eliminate all bugs and produce a better product. However, Microsoft also has a history of producing products that are bug-ridden and full of annoyances and incompatibilities with previous releases. That said, they also have a history of increasing the stability and usability of their products over time with patches and service packs. Windows XP SP2 is the most stable OS I have ever used. Microsoft is not alone in the software world when it comes to releasing buggy code, they just seem to have the most scrutiny. I think that Windows Server 2007, whenever it is released, will have its share of the expected issues that people have come to know and associate with Microsoft. However, I think that future patches and updates will turn into a server OS that will be a proud successor to Windows 2003. Should Microsoft delay it? History says it won’t matter, but there is a first time for everything.
-VMware expert Andrew Kutz via email
According to the article in question, it sounds like the delay is not that significant. My theory is that this was done to allow some synchronization of code between it and what’s going into the updated Server Longhorn beta. Another thing comes to mind when you said “controlled test environment”. There’s a lot of things in Virtual Server that are going to become key technologies in Longhorn Server, and the better they have those things working correctly ahead of time, the easier it’ll be to build the bigger and more important infrastructure of Longhorn around them. VS 2005 R2 SP1 has been hanging over people’s heads for a while, and I suspect they wouldn’t do that unless a) they wanted to make sure installing it didn’t sour people’s experiences with VS 2005 in general, and b) it contained some key things that were going to be rolled forward into Longhorn, and they wanted to make sure those pieces worked properly right now.
-Microsoft Virtual Server expert Serdar Yegulalp via email
You can read virtualization management expert Anil Desai’s thoughts on his first blog post, Viridian – Better Late than… Early?