In addition to liking the end-result, I was also proud of the fact that I used only Free and Open Source (FOSS) software running on Linux to do the job. When describing the process to colleagues, I would get the suitable (or perhaps simply polite) responses of “cool” or “wow.” It wasn’t until I was talking to a tech-savvy cousin at a Christmas party that I got a reality check when he said, “Yeah, I just use a Mac.”

Defensively, I quickly countered that I didn’t want to be forced to use a graphical interface, that the command line allowed me to script the process, and that I felt that I had much more control over the authoring process by using command line tools.

Over the past week, I have been reflecting on this conversation. While I stand by my counter argument, I don’t feel that it captured the essence of why I went the Linux/FOSS route. (I should note that I did use the graphical tool Kino to separate the video into chapters; the various command line tools were used to create the menu system and to burn the DVD. I’ll write about the details in a future post.)

I’m fairly certain that had I used commercial software (e.g., on a Mac), I would have been able to author a DVD in short order. However, I’m not sure I would have gained as deep an understanding of the process as I did by gathering the various utilities from across the Internet and “doing it myself.” Sure, it was a bit of a steep learning curve at times, but by knowing more about the nitty-gritty details, I think I ended up with a better result. I also had the option of modifying the code if it didn’t suit my needs. It was empowering to have so much control over the process.

4. AUTOMATIC UPDATES The Software may communicate with Google servers from time to time to check for available updates to the Software, such as bug fixes, patches, enhanced functions, missing plug-ins and new versions (collectively, “Updates”). By installing the Software, you agree to automatically request and receive Updates.

I don’t mind the software checking to see if there are updates available; I do mind if these are automatically installed. I can’t tell from their wording if “receive Updates” means both download and install. Two issues come to mind with this kind of mechanism. First, an automatic update mechanism is a potential vector for infection. Second, I may not want the update as it may remove a feature or cause an incompatibility with other software installed on my computer.

It should be noted that the GWT is not without privacy concerns. As clearly stated by Google, hosted mode does send some information back to Google:

Privacy notice: When you use the Google Web Toolkit’s hosted web browser, the application sends a request back to Google’s servers to check to see if you are using the most recent version of the product. As a part of this request, Google will log usage data including a timestamp of the date and time you downloaded the Google Web Toolkit and the IP address for your computer. We won’t log cookies or personal information about you, and we will use any data we log only in the aggregate to operate and improve the Google Web Toolkit and other Google Services. Please see the Google Privacy Policy for more information.

Since this information is only sent in hosted mode, it will mostly apply to developers. A deployed system would use web mode which does not appear to contact Google. Of course, depending on the security requirements of a deployed application, one would want to audit the generated JavaScript and HTML code as a bug (or worse) in the GWT could lead to security holes. To see what I mean, read the classic Ken Thompson’s ACM Turing Award lecture, Reflections on Trusting Trust (PDF).

While this kind of technology has been around for a while, the fact that Google has published their own toolkit may lead to a de facto standard. I expect to take the GWT for a spin soon.

Another defenseless gadget has fallen prey to the relentless march of the Penguinistas. Tim Riker’s eLinux.org [link] website has published extensive, detailed instructions for creating a cartridge that can boot any unmodified Mattel JuiceBox into a Linux-based environment.