The 'Dirty Little Secret' About Longhorn

evelopers say there's a dirty little secret about Longhorn that few Softies are discussing publicly: Longhorn won't be based on the .Net Framework.

We're still expecting that the .Net Framework will ship with Longhorn–on the CD and/or "in the box" in some way. But the .Net Framework won't be at Longhorn's core, we hear.

Instead, the .Net Framework will be the core for a small subset of Longhorn, specifically the WAP (Windows API Platform), which consists primarily of the "Avalon" Windows presentation system and the "Indigo" Windows communications system.

[rank=www.extremetech.com/article2/0,1558,1821110,00.asp]Full Article[/rank]

[rank=www.microsoft-watch.com/article2/0,1995,1820607,00.asp]Full Story on Microsoft Watch[/rank]
 
Well, a .NET core would mean that they would have huge performance issues. There is no way that a JIT compiler can match pure machine code, at least not at this point of time.
 
:S :S :S :S :huh: :huh: :huh: :huh: :no: :no: :ashamed: :ashamed: :ashamed: :ashamed: :ashamed:

I did not understand a word of what was written..... Shows my ignorance to .NET and all that.

I will be happy if someone can explain what the big deal is abt this .NET thingy not being there in Longhorn.
 
Well, currently the core of WinXP/2K is Win32 (the system+userspace calls/Standard libraries/sort of the MS equivalent of POSIX)
Talk was that longhorn would replace them with .NET functions.
But that hasn't happened.
 
Back
Top