Here is a snapshot I took during today's trip to Chapters @ Rideau. While walking out, the placement of some books caught my eye: Note the "headlines" in the background of the Vista books: "Ailments and diseases". Certainly unintended and a bit childish, but I found it hilariously funny :-)

Everybody seems to be crazy about Chrome, the new superfast Google browser. The odes on speed sounded quite exaggerated, so I had to try it. I opened up again my old battered Fujitsu Lifebook and after 3 reboots (it was not used for about 2 months and Windows update had to have its patching done) I downloaded and installed it. The rumors were not unsubstantiated ... it IS considerably speedier than anything else, including Opera.

One feature that I strongly miss from Objective C are namespaces. Inability to avoid name clash between your classes sometimes really stands in your way. I am reading S. Kochan's book "Programming in Objective C" and in one of the examples he creates the class Point. Unfortunately, there already is struct Point defined in mactypes.h. The solution is easy - rename the darn Point to something like TKPoint ... at least that is what Cocoa naming guide recommends.

PM Xcode[34563] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: ' *** -[NSAutoreleasePool stopObservingModelObject:]: unrecognized selector sent to instance 0x32da240'

A friend made me aware of this (thanks, Peter): The Inside Deets on iPhone 2.0.2 and Dropped Calls http://www.roughlydrafted.com/2008/08/28/the-inside-deets-on-iphone-202-and-dropped-calls/ Sounds like plausible explanation. It is not the network that is fault but the interaction of the bad power control algorithm in 2.0 and 2.0.1 software and the network that is at fault. The sooner everybody is running 2.0.2 software the better things will be. Having seen the graphs the 2.0.2 software has already