My heat at home had been working sporadically for a week or two before it finally decided to quit working altogether earlier this week. My landlord came by this afternoon and poked at it and a couple hours and a visit from an electrician later he's found a broken solenoid or something like that. Apparently those can't be purchased on weekends, so I'm going to be cold till Monday. I'll just pretend I'm in Lambeau Field when watching the Super Bowl tomorrow, I suppose.
Actually, it's a good thing I'm in the Bay Area rather than, say, Boston. When I say it's cold here, that means it gets down to 62 or so without the heat. If we had a sudden cold snap it'd be another story, but even if that happened I wouldn't be able to leave my ice cream out in the living room without having it melt.
A big part of the plans behind the Rotor (aka. Shared Source CLI) project was for a community to develop around the variety of projects that were possible with the release of the code for the core of .NET. A web site went up at sscli.net and a few projects got off the ground, but the interest quickly dwindled.
Every so often I'd point people to the browsable code at sscli.net, where they could find good examples of how to implement various Win32 APIs on FreeBSD and Mac OS X. But when I went to the site a few weeks ago, it was down. It has stayed down, and I don't have any way to know when or if it'll come back up. I wonder if anyone other than me has noticed.
The Shared Source CLI site at Microsoft is still available, but all it includes is the tarball for the Rotor 1.0 release. That means it doesn't have browsable code, it doesn't have any of the side projects, and it doesn't have things like my changes to get Rotor to build under Panther.
Maybe Microsoft will build a new version of Rotor when the next release of .NET is out. If they do, hopefully the community around that release will last a little bit longer than this one did.