I've been completely unconnected for four days, so I'm sure that Joel’s essay on the differences in culture between Unix and Windows programmers has been blogged to death, like most of Joel's essays. However, I was a Unix programmer for 4 years before becoming a Windows programmer, so this one really spoke to me. I especially like his description of how programs act under Unix so that they can communicate with other programs (success produces no output) vs. how they act under Windows so that they can communicate with people (success produces output). I don't know what I'm going to do with these new insights, but I'm enjoying them nevertheless.
Here. Brad Abrams describes how the Whidbey .NET Framework adds support for tracking unmanaged memory and limited resources of a non-memory nature. The former is handled by informing the GC of added "pressure" associated with unmanaged memory and the latter by exposing the private HandleCollector class that .NET 1.x has used for a while now. It's not reference counting, but it'll do for a start... : )
“Quentin Clark provides an overview of WinFS, including what benefits it produces, what it is, and how it’s put together. This episode introduces WinFS as a basis for more detailed presentations.”
And than Nathan posts another sample showing off the various kinds of resources to be defined in Avalon and how to define them on top of one another. I’m loving this guy!
BTW, this is post 1000 on this feed. I can’t keep up with Scoble, of course, but I had no idea I was *that* wordy. : )
Here. Nathan Dunlap kicks off his new Avalon design blog with a sample on how to clip video to arbitrary shapes. I don't know for what I'd use this, but it's nice to know it's there. : )
And from heaven, the thing that budding Longhorn programmers most need falls to earth. Nathan Dunlap, a designer on the Avalon team, has taken up blogging. He's covering design tips as someone that understands Avalon *and* design inside and out. Welcome, Nathan! Subscribed.