A look at the leaked Longhorn

Generally I’m not a proponent of deep analysis when it comes to alpha-level software. But so much furor has erupted about the recent alpha release of Longhorn, I figure it’s worth some type time. For those who missed it, Microsoft leaked Longhorn’s Build 4053 and half the world is excited about its feature set whereas the other half is throwing tantrums over its resource requirements.

Free IT resource Open Source Business Conference (OSBC) May 22-23, 2007 Sponsored by OSBC Free IT resource TechNet: More ways to know it, share it, and keep it running. Sponsored by Microsoft

Features first. I was simply gleeful about the install process. For an alpha Microsoft build, I had a whole Advil bottle ready in reserve, but the thing ran smoothly with a sexy new interface that makes the old DOS windows a memory. It’s similar to XP’s largely unattended backup after the initial round of questions. Enter your answers, hit the start button and go watch TV -- which you’ll need to do because this install takes quite a while. Again, we’re talking alpha.

That's even more important to remember when you’re up and running, because my Longhorn pretty much just emphasized the "long," as in "long time to do anything." Do not expect a system with snappy response -- a problem many early reviewers are yodeling about online, to which I can only point out two details: one, Microsoft; two, alpha!

Instead of worrying about response times, take a look at the alpha feature set. That’s what it’s all about, and Microsoft doesn’t disappoint. You’ll find a new side-mounted tool bar/system tray/icon smorgasbord. I’m not a big fan of these things, because I always figure that’s why we have a desktop, but it’s a stylish-looking bar and certainly sets Longhorn’s interface (code named Aero) apart from XP.

Something else that sets Longhorn apart is its version of Internet Explorer. A slick new set of graphics is coupled with improved performance (even in the alpha version) and some new features (such as a Download Manager and a bundled pop-up blocker) that are worth something. All this is integrated nicely into the Aero style along with improved integration for features such as the photo and video library. I like this theme Microsoft is now using, but rumor has it that the company has really listened to customers on the theme front and that we’ll see improved support for theme mods when Longhorn’s really riding the range. Should make system administration a real treat when you’re saddled with mod-happy power users.

What I’m still waiting for, however, is a complete picture of what WinFS will look like. Build 4053 includes pieces of the new file system, but it’s lacking in the full, promised WinFS feature set; you can see more of it in previous builds. This version really only shows you surface glimpses of this technology, making it more of an interface reality check than a full peek at Longhorn.

So you’d think 4053 would run light, wouldn’t you? But you’d be wrong and here’s where we get to the piggy portion of our dialog: Build 4053 has a bit of resource problem, namely a RAM footprint of 483MB. And if you’re thinking “Wow, that must have spawned some dirty talk on the Web,” you’d be right. But let’s all take a deep breath and think rationally for a moment. Sure, this sounds like another invitation by Redmond to foment a user jihad, but what are we really running? Yet again, the answer is alpha.

Honestly, you can barely make an accurate performance prediction about a Microsoft product when it’s in pre-patch version 1.0, so how accurate can an alpha build be? Trust me: RAM requirements won’t be a half-gig when this puppy sees daylight.

And by the way, that day will most likely be somewhere in 2006. PCs with 256MB are selling like hotcakes right now, with 512MB also becoming a mainstream number. Where will RAM rates ride in 2006? We can only guess, but I’d say 1GB being popular is a safe bet. And lest we forget, selling more hardware is an accepted part of the Microsoft mission, so I’m not sure why increased resource requirements in Longhorn would come as a shock. I’m not overjoyed to hear it, of course, but after 15 years, I can’t say I’m surprised. With a clean interface, slick graphics, and (we hope) some real attention paid to security issues, I suppose I’m resigned to taking the bad with the good.