Microsoft scales back plans for Longhorn

Microsoft Friday made a dramatic retreat from its lofty goals for Longhorn, saying its highly touted storage subsystem would not ship with the client operating system.

Instead, Microsoft said WinFS storage and search technology would be in beta when the Longhorn client operating system ships in 2006. This is the first time Microsoft has confirmed a ship date for the client operating system. The server version remains slated for 2007.

In addition, Microsoft said WinFX would be back-ported to Windows XP and Windows Server 2003 and made available when Longhorn ships. WinFX replaces the Win32 programming model and includes two foundation technologies slated for Longhorn - a presentation subsystem called Avalon and Web-service middleware called Indigo. In essence, this announcement dilutes the importance of those two technologies to the Longhorn platform.

To continue reading, register here and become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

Microsoft Friday made a dramatic retreat from its lofty goals for Longhorn, saying its highly touted storage subsystem would not ship with the client operating system.

Instead, Microsoft said WinFS storage and search technology would be in beta when the Longhorn client operating system ships in 2006. This is the first time Microsoft has confirmed a ship date for the client operating system. The server version remains slated for 2007.

In addition, Microsoft said WinFX would be back-ported to Windows XP and Windows Server 2003 and made available when Longhorn ships. WinFX replaces the Win32 programming model and includes two foundation technologies slated for Longhorn - a presentation subsystem called Avalon and Web-service middleware called Indigo. In essence, this announcement dilutes the importance of those two technologies to the Longhorn platform.

“I question what is left of Longhorn. I just don’t know until we have more details,” said Peter Pawlak, an analyst with Directions on Microsoft, an independent research firm. “What will be the difference [in Longhorn] from a Windows XP box with WinFX?” says Pawlak.

The move to expand the platforms that support Avalon and Indigo means developers will have a lot of the newfangled Longhorn infrastructure to write applications against without having to worry about users adopting Longhorn to take advantage of the applications.

The changes make Longhorn more of an evolution from Windows XP rather than the revolution in desktop computing that Microsoft has been touting, Microsoft officials admitted.

“The path to get to our very ambitious vision for Windows is different and is more evolutionary in appearance rather than one big leap like we have described in the past [with Longhorn],” says Greg Sullivan, lead product manager for the Windows client group at Microsoft.

But Sullivan did say Longhorn would be distinct from Windows XP and Windows Server 2003. “There will be differentiation features available in Longhorn, from the fundamentals of the core OS kernel, to performance, reliability and security and a host of management tools and an error-reporting infrastructure - all the things that IT is interested in.” He said Longhorn would ship in the second half of 2006 and would be “broadly available” by the end of that year.

He added that “Longhorn will bring tremendous strides to achieving the Windows platform vision, and subsequent to that we will get out WinFS and we will get to the vision that we outlined at the PDC.”

At its Professional Developers Conference in November, where Microsoft distributed a pre-alpha version of Longhorn, Microsoft’s chief software architect Bill Gates said Longhorn would provide opportunities for developers that would be stronger over the next decade than at any time in history.

Now that seems only like tough talk as Longhorn’s key constructs will clearly develop on a more gradual schedule.

That makes sense, according to some experts. Microsoft has always relied on its development community to generate excitement around a new technology, which is how it began to roll out .Net.