According to Computerworld, Don Norman, the design engineer famous for such works as “The Design of Everyday Things,” is consulting on Longhorn UI design. Cool! I especially love this statement:

“This is not the ‘computer age’ any more; this is the age of very smart chips hooked into a huge worldwide network. Infrastructure is about sharing.” This means two or more incompatible ways of doing things is counterproductive.

I love his characterization of client computers as “smart chips,” i.e. storing services and data production on the server, although the “smarts” of the client is important, too, i.e. data visualization and manipulation (which is death with a round-trip per click).

In Ian Griffith’s latest post, he shows 3 identical (to my eye) upper case Os next to each other and says, “[t]his clearly shows the shortcomings of that implementation” like a normal human can tell the difference!

The funny thing is, I’ve actually noticed that ClearType on Longhorn was generally better, although I never knew if that was my imagination or not. The thing I love about Ian is that he takes that vague sense of “this seems better” to “let me show you why it’s better and I’ll show you my own implementation of ClearType as a comparison just for fun.” What’s not to love? : )

After weeks of trying research, floating his thoughts on his blog and taking feedback from the blogging community (including several Microsoft folks), Jon Udell has posted an Infoworld article digging into the pillars of Longhorn (Avalon, Indigo and WinFS) and grading them on their implications. He summarizes nicely, I think:

“Indigo, by virtue of its developer-friendly simplification of Web services protocols, could propel Microsoft into the forefront of enterprise middleware. Although Longhorn’s use of Indigo will focus on networks of Windows peers, the technology isn’t bound to Longhorn. Expect to see Indigo-powered ‘enterprise service bus’ offerings from Microsoft and partners.”

“If WinFS succeeds in delivering improvements in users’ ability to organize and manage local information, enterprises looking to drive productivity up — and support costs down — will want it. The wild card will be the level of support for legacy document formats and emerging XML formats. Benefits that accrue only to new WinFS-aware applications won’t tip the scale.”

“Avalon’s TV-like ‘presentation experiences’ clearly favor the home entertainment center over the business desktop. An accelerated convergence of voice, video, and data could alter that equation, and Avalon is designed to help drive that convergence. But enterprises concerned about reach and lock-in will need to carefully evaluate the trade-offs.”

I think that Jon’s nails the tensions involved in Indigo and WinFS, but misses the boat on Avalon, which represents a much-needed overhaul of our aging presentation sub-system and enables a host of applications that we need to visualize and manipulate the ever increasing amount of data with which we deal. Of course, the existing presentation stack will continue to work just fine, but for those applications that need it, Avalon will be a god send. As we progress over the next decade, more and more apps are going to need what Avalon provides.

However, while I don’t agree with every that Jon says, but I do appreciate the thoroughness that went into his opinions. Folks involved in Longhorn, both inside and outside of Microsoft, should take a look.

According to legend, half the Windows XP BSODs are 3rd party driver crashes, reducing our “trustworthiness” to the user (trust is more than security and privacy). Yesterday, DevSource reported on a new driver model in Longhorn that will isolate the OS from driver crashes and simplify the development platform to reduce crashes in the first place. Amen, brother.

[via Dactylmatrix]

Daniel Lehenbauer, an SDE on the Avalon team, has a nice explanation of the 3D coordinate space in Avalon with some very illustrative pictures. I’ve got absolutely no experience with 3D and I can follow what he’s talking about. Looks like Daniel should be writing a book…

Tim Sneath, a .NET Architect in MS-UK, lays out the audiences and tensions of MSBuild very nicely in this short summary. If you want more information, there are a bunch of MSBuild resources on the Longhorn Developer Center’s Tools & Code Samples page.

Does anyone have a VPC image of Longhorn 4074 (the WinHEC Build) that they could share with me? Every time I try to install, it crashes the VPC. Normally, I wouldn't ask (I have a machine just for Longhorn), but I have the need to run the latest public and the latest internal builds. Thanks!

Facetop has been all over the web for a couple of days and I’d like to point out two things about it:

1. This is exactly the kind of thing we’re enabling with the advanced client capabilities in Longhorn that you just couldn’t do in a web app. Until you see something like this, you don’t think of it, but when you’ve got advanced capability in the platform, all kinds of cool stuff happens that the creator of the platform (Apple’s Mac OS X, in this case) never considered. I fully expect the coolest Longhorn apps to come from someone outside of Microsoft.
2. I want it!