Materials from my SQL CLR talk are here and from my Data Mining with Analysis Services 2005 and Excel 2007 talk are here

Another day, another VSLive. This one was the 4th show of my 12th year speaking at the conference. Yow! Anyway, the slides and code from my talks are available by clicking here.

I am writing this post in Word 2007, running on Windows Vista “Pre-RC1” build 5536. The new Vista build is amazingly fast and stable. The new Word is really a great place to work. The UI improvements in Vista are wonderfully ergonomic and fun, and my laptop’s video card can’t even handle “glass.” I had expected much less from Vista, and much more disruption in Word. A pleasant surprise. I think Vista will be a compelling upgrade for the mainstream.

The State of Massachusetts has decided that they will continue using Microsoft Office but will make OpenDocument format (ODF) plug-in part of the standard install.

The irony is uncanny: in an attempt to be politically correct in support of open file formats, the Commonwealth's CIO has decided to tell people to use the world's de facto office software suite, but optionally (?) save their files in a format that may not maintain the full fidelity of the documents themselves.  The irony doesn't stop there: it turns out that Microsoft Office, rather than OpenOffice, is in fact the politically correct choice, given its richer accessibility features (i.e. features for people with vision, hearing and other disabilities).

That OpenOffice lacks these accessibility features cuts to the core failing of open source software: without a regular, paid staff of developers, some of the nitty-gritty features, the ones that are less "sexy" and which appeal to a minority of users, just don't get implemented.  With commercially developed software, people get paid to do what others might consider grunt work, and they get reviewed based on their performance on this work.  So it gets done.

The failing of OpenOffice will become more apparent once Office 2007 is released.  And maybe OpenOffice will respond, within two years or so, with something representing feature parity.  But playing catch-up isn't a software development strategy; it's a grudge match.

I just got my Treo 700w to sync over Bluetooth.  And I am very proud of myself.

But, in a technologically sensible world, I shouldn’t be…that is to say, setting up an ActiveSync partnership over Bluetooth shouldn’t be that hard.  In fact, there shouldn’t even be a concept of setting up a “partnership.”  I should just be able to tell ActiveSync to allow Bluetooth connections and go.

Instead, I have to go into the Bluetooth stack software on my laptop, enable the serial port profile, determine its COM port in the property sheet, go into the ActiveSync Connection Settings dialog, allow connections to that COM port, pair the phone with the laptop’s ActiveSync profile, fire up ActiveSync on the device, and then, finally, tell it to connect over Bluetooth.

Bluetooth was initially designed to replace the cables used to connect PCs and peripherals.  But until Bluetooth is as easy to use as a USB cable, it will be relegated to a specialized protocol for cell phone cordless headsets.  People will plug and play with cables until playing unplugged doesn’t require voodoo or passing a certification exam.