My first week with the iPt has been a thorough validation of my decision to jump ship from the Palm platform. The things this new device doesn’t do are still a problem, but the things it does do it does incredibly well. I won’t gush over those because they’ve all been thoroughly gushed over. But anybody who thinks the success of the iPhone/iPt platform is primarily based on superficial factors of appearance or brand image likely hasn’t used one for more than two minutes.

I bought a new Netgear wifi router for the house today, to replace a crappy old D-Link that didn’t really work with either my MacBook Pro or my new iPod touch.

A business-card-sized slip of paper fell out of the box when I opened it. It was a little GPL/LGPL notice, with a URL for downloading source. Digging further through the included paper I also found a three-panel insert with six-point type that has the full GPL text on one side and the full LGPL text on the other.

I bought my Palm TX in December 2005, a few months after it came out. In my blog post where I weighed the pros and cons of the device and the platform, I grumbled that “Palm has successfully crushed any optimism I might have had for fixes appearing in the form of a free, downloadable OS upgrade.” My grumpy intuition was right – in fact, the Palm platform has pretty much just stagnated since that time, punctuated with spastic feints toward Linux that you can read about elsewhere or in my old Palm-related posts.

Most readers are probably familiar with the fact that companies or organizations sometimes post “bounties” for open source products, or features, that they would like to see developed. Implement the thing to their satisfaction, you get the bounty – and the community gets the code. Sweet.

A while back I started gathering references to these things, thinking I’d start a site that listed them, made connections between coders and sponsors, etc.

For several years I maintained a hodge-podge of little web-based utilities at toolbot.com. Recently I decided to wipe the slate clean, bringing things back selectively. One of the few that I missed personally was my weather site. It returned National Weather Service forecasts in response to compact URLs of the form weather.toolbot.com/05667, for any five-digit US zipcode.

Originally, the site worked by scraping plaintext forecast files on the NWS servers. Eventually those went away; I looked at and gave up on the arcane (to me) SOAP interface that superseded them. All I wanted was a damn weather forecast, without ads, via an easy-to-type-no-matter-where-I-am URL.

In 2007, I took a whack at learning Haskell as my Language of the Year. It was an educational experience on more levels than I had expected. I didn’t get as far with the language as I might have hoped, but I did have the essential mind-opening experience of dealing with a purely functional, “lazy” language. My approach and style in my primary day-to-day language (Python) changed in a positive way. I really like Haskell and hope to continue playing, and possibly working, with it in the future.

Update: As of 2012, the primary Django repo is on GitHub. The mirror described in this post has been retired.

Just wanted to post a quick note that I’m now publishing an experimental Mercurial mirror of the Django source code repository, including all tags and branches and even the djangoproject.com website source itself. Tom Tobin at The Onion has been maintaining a similar mirror of Django trunk for a while (and very helpfully answered some of my questions in IRC), but I wanted to do the whole tree.