Slashdot Mirror
Microsoft Lifts Curtain on Indigo Software
daria42 writes "Microsoft has released an early version of Indigo on the Microsoft Developer Network. Indigo is a new communications system intended to let Windows programs more easily connect to other software. Indigo was one of the three original "pillars" of Longhorn, however under the new plan it will be re-tooled to work with Windows XP and Windows Server 2003, in addition to Longhorn."
After Microsoft back ports everything from Longhorn to XP, will the $499 upgrade from XP to Longhorn be like 95 to 98? Just some bug fixes and a free browser?
it is only after a long journey that you know the strength of the horse.
I've got a great idea. Now that all the DCOM holes have been plugged (either at the OS, or at the firewall, or both), let's pick a new port number that'll be open and listening to the world by default, and on which all the OS components will have to rely.
For bonus points, I'll justify this by saying that it makes something that sounds really cool on paper if you're a CTO, but is actually the first line from the functional spec for "A platform for writing remote exploits" to anybody with even a millineuron of cynicism left in their brain.
For ONCE, I want a newer version of Windows to be faster and smaller than the previous version and more stable as well.
Windows 2003 actually satisfies that requirement, by a solid margin.
However, Microsoft never decided to release it in a non-server version... And if you've never tried running a server version as a home version, well, you have no idea how many otherwise "free" (as in beer but not speech) programs will refuse to run.
As an aside, you can trick 2003 into identifying itself as XP with only two tweaks to the install CD. I will not disclose them for fear of invoking the Legal Wrath of the Gates, but with a Google search for similar hacks to Win2k, you can probably figure out what to change. And no, the well-known product version switchers out there that worked on 2k will not work, and will actually render your system unbootable if they manage to do anything at all. Really, trust me on this, I tried both of them.
Everything in Longhorn will be based on the .NET framework and sandboxed, with the Win32 API scrapped. Longhorn's ability to run the Win32 API will be through a compatibility layer, similar to the DOS compatibility layer in XP. However, WinXP's ability to run Indigo and Avalon, the two pillars of Longhorn, will be done through a forward compatibility layer.
Fortunately, they're doing everything clean this time with XML and SOAP, with an open API, as opposed to binary-only files, arcane RPC calls, and endless piles of undocumented, insanely messy code dating back until the early 90s. There actually might be some interoperability this time around -- Longhorn SAMBA certainly won't be nearly as hard to code and reverse engineer, especially with Mono in hand.
More details: http://msdn.microsoft.com/Longhorn/understanding/p illars/default.aspx
- - - - - Fear not the reaper, but my shiny white teeth.
I'm going to have to agree with the parent poster. I work at MS, and just recently saw a pretty thorough ppt on Longhorn features, a lot of which didn't depend on the pillars. It took an hour just to talk about all the security revamps in the kernel. Unfortunately, its all 'MS confidential' for now... The first Beta should be out during the summer, lets reserve our judgements of Longhorn until then.
For centuries, Indigo used to be a very valuable dye; the exclusive looking deep blue color was a sign of wealth. Of course that "exclusivity" went down the toilet when they developed synthetic indigo in 1905 and everyone with a new pair of blue jeans could have some of that exclusivity.
It sounds like a good name for a Microsoft product.
but I was always under the impression that Server 2003 and XP were akin to Windows 2000 and 2000 Advanced Server?
Yes and no...
From a high-level view, 2003 roughly corresponds to the "server" version of XP, which itself equates to 2000 Pro.
For Win2k, however, every version used the same underlying OS, with only the list of installed products (and a few config details) changing with the server-ness of the product you installed.
Windows 2003, however, Microsoft actually released as NT 5.2 (compared to XP as NT 5.1, and Win2k as NT 5.0). Now, version numbers don't mean a whole lot, but with Win2k3, Microsoft actually did optimize it both in terms of memory footprint and CPU efficiency. As an example, you can just barely fit a hand-trimmed XP installation into a 96MB RAM footprint. Win2k3 you can do in half that, under 48MB (without running server-specific services and applications, of course), comparable to the footprint of a baseline NT4 Workstation installation.
And don't think you give up speed for that - Not even close. 2003 not only "feels" quite a lot more responsive, it actually does run arbitrary code faster... I don't know how (perhaps XP has that much bloat?), and I had to write a dozen or so small test apps to prove it to myself, but you'll easily see a 10% gain even on mostly CPU-bound tasks, and I frequently notice that multiple I/O bound tasks that on XP would take time 2X, take around 1.1X on win2k3.
And for stability... Wow. I thought Win2k took a huge leap forward, and XP a big-but-not-so-big leap back, until I started playing with 2k3... You just can't crash those things! On one of my servers at work, I have an uptime over a year, and it hasn't even started getting flakey! Almost as good as a BSD box!
And no, I don't work for Microsoft... I even prefer Linux, myself. But, finding myself more-or-less forced to use Windows, I REALLY wish MS would release a pro or WS version of Win2k3 (my particular hack works for now, but I kinda wonder how Win2k3 SP1 will react to my trying to install it on a nonexistant product line... With luck it'll work just fine, but I expect I'll need to slipstream it in and do a clean install, sigh).