Here.

Rich Turned, an Indigo PM, has some useful things to say about Indigo in his recent Channel9 videos:

• What is the biggest misperception of Indigo?
• What is your advice to developers who are thinking about Indigo and interoperability?
• What would be the first thing about Indigo that you’d show a Visual Basic programmer?

Plus, Rich has a blog to which I subscribe (but I wish he were more prolific).

I’m really loving Jon’s approach to exploring and questioning the goals and implications of Longhorn:

1. Questions about Longhorn, part 1: WinFS
2. Questions about Longhorn, part 2: WinFS and semantics
3. Questions about Longhorn, part 3: Avalon’s enterprise mission

I don’t have any pithy summaries of his basic points; his posts deserve a read and a think.

This post is an oldie, but a goody, in which Kenny Lim talks not only about custom Avalon controls catching property changes so that they can re-render themselves, but also about the custom measurement sequence, which is a core piece of a control that does custom layout like, say, a pile of cards (hypothetically, of course : ).

VisitorVille maps your real-time web site data to a SimCity-like environment that you can use to see where folks are going on your site and how they’re navigating from one place to another. It does the other web traffic kinds of analysis, too, but the ability to watch your visitors in real-time looks pretty darn cool. This is the kind of thing that Longhorn should be good at enabling.

[via Jason Whittingon]

Richard Turner, a PM on the Indigo team, addresses the biggest misperception about Indigo in this Channel9 video.

Bottom line: Microsoft is not taking MSMQ, COM+ or Remoting out of the platform; it’s just that Indigo, which subsumes the features of these other technologies, will do it all better.

Daniel Lehenbauer, an SDE on the Avalon team, has started a wiki providing helpful hints on using XAML as your new 3D file format and has provided a utility to help those playing with 3D in the WinHEC build of Longhorn (build 4074).

Jon Udell, a writer for InfoWorld, begins a series digging into the value proposition of Longhorn with a look at WinFS. Jeremy Mazner, a Microsoft evangelist focusing on WinFS, provides a counter-point.

Here.

I was recently asked to characterize the attendees of a typical DevCon and this is what I said:

The attendees of a DevCon are the top of the pyramid developers that not only try new things all the time, but also make design and architecture decisions for their employers and customers. Also, all of the speakers, i.e. experts in their fields, practitioners, vendor architects, etc, are also attendees, and it’s wonderful to see them heckling each other.

The environment of a DevCon is one big room with everyone in it, so it’s a shared experience front-to-back. As soon as any talk is over (I keep them at 45 minutes to get the maximum number of new ideas into people’s heads), the buzz between people starts and only stops when I introduce the next speaker (loudly : ).

A DevCon is a wonderful mix of movers and shakers, vendors, enthusiasts, architects, practitioners and and a conference with an atmosphere and a set of attendees unlike any other that I’ve attended.