I launched this blog in July of 2005. It was powered by a homebrew PHP5 creation that as of today has, finally, thankfully, been laid to rest.

The other thing that started absorbing my attention in July 2005 was Django. Every month since then, I’ve thought, “You know, I should make some time this weekend to port my blog over to Django.” I was using it for everything else, after all, side projects as well as web applications at work. The word “port” was the mistake there – if I had said, “I should make some time this weekend to destroy my old blog and make a clean-slate Django version”, I probably would have gotten it done about two years ago!

Another successful session of non-stop technical chatter in the back of our favorite chain restaurant. Links and commentary:

• The Talk Like a Pirate Day site was a victim of its own success this year. After several hours of record-breaking traffic, Chris nobly disabled the site to protect paying customers on the server. I’m looking forward to the white paper, “How to serve one million unique visitors one day per year”. We also heard the origin story of Talk Like a Pirate Day and the site. I hadn’t realized what a pioneer and international pirate celebrity Chris was.

Lately I’ve been trying out the Mercurial distributed version control system on some real projects.

I currently use Subversion for production stuff at work. It’s reliable, has great Trac integration, and is most likely to be known by other developers. (In fact, we hired a new person at work this fall who will be helping me with web development, and it turned out that Subversion was what he was familiar with. So I feel vindicated on that last point especially.)

First alpha release of Python 3.0 (formerly Python3000) is out today. And it even works! Gotta do something about that executable name, though…

$ ./python.exe 
Python 3.0a1 (py3k, Aug 31 2007, 15:11:11) 
[GCC 4.0.1 (Apple Computer, Inc. build 5367)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>>

(Download, What’s New)

The biweekly Western Massachusetts Developers Meeting was small tonight, but still high-quality. Topics in our typically rambling discussion included:

• Are crawlers from some search engines following links embedded in Javascript (i.e. Ajax) code? And if so, what’s the use?
• What should Chas use for a CMS? (I don’t think any conclusion was reached; the two leading contenders seem be “build it in Django” or “just use Drupal”.) I do appreciate the argument that sometimes it’s good to think of yourself as a regular ol’ “business user” rather than someone who custom-develops everything just because he can.
• When does testing happen in your process? A range of answers here, from “before I write code” to, well, a bit later in the process.
• XPath and XQuery are worth knowing if you touch XML
• Various WTFs, including the company that replaced their SQL database with a single gigantic XML file because XML was, you know, magic.
• Google searches that find embarrassing mistakes. (It’s been a while since I updated that page)
• Another round of olde tyme computer reminiscences, prompted by my “Home Computer Handbook” from 1978. (Chris knows EBCDIC!) Have you ever heard of SLIP, GPSS, or SIMSCRIPT?
• Another round of version-control appreciation (Subversion and svnmerge, Darcs, Mercurial)
• Is there any OS X web design application somewhere between Coda and GoLive or Dreamweaver? I.e., not bloated, but still pleasant to use for people who need some WYSIWYG editing (my students)?
• BBEdit: What’s still good about it? (Palettes for nontechnical users.) What’s bad about it? (Kitchen-sink approach to multiple language features.) Make no mistake, though, BBEdit was definitely cool back in the day.
• The scriptaculous Ajax in-place editor
• Will inaccessible (in the Section 508 sense) web pages become more widespread now that the argument against them is being reduced from “What about all the crappy browsers out there, and what about accessibility?” to “What about accessibility?”

We also agreed to try doing some lightning talks or similar short presentations at a future meeting. I think this could be very cool. Chris said he would volunteer to run the gong.

From Apple’s release notes on the latest QuickTime update (emphasis mine):

QuickTime 7.2 addresses critical security issues and delivers:

• Support for full screen viewing in QuickTime Player
• Updates to the H.264 codec
• Numerous bug fixes

Finally! Now Steve Jobs can rest easy, knowing that nobody is going to pour boiling-hot coffee on him. Not over this, anyway.

---

Peter commented on Thu Sep 6 12:47:52 2007:

Finally, I have the habit of clicking twice on the quicktime screen to get a full screen mode but it never worked. Honestly thats one reason why I do not like the program very much. Guess I will download the new software right away. Thanks

At the end of this old post by John Nack at Adobe I found corroboration of my feeling that putting “RAW” (as in, raw image files from digital cameras) in all caps is silly. Some might feel this is a level of detail that only concerns copy editors and trademark lawyers, but I’m like that sometimes.

I’ve always preferred the nice, simple “raw” as the term for this sort of format. Saying “RAW” seems a little aggro (“RAW is WAR!!”), like you need to make the little devil-horns with your hand while saying it. The term is neither an acronym (RAW) nor a proper name (Raw), but rather a generic descriptor for a whole class of formats. Therefore Adobe just says “raw.”