Automation Adventures

Google has released their beta browser Chrome for Windows. It distinguishes itself from other browsers by having a very minimalistic design, and some interesting technological features:

• The address bar doubles as a search box, history browser and suggestion bar.
• The tabs can be dragged out of the browser to create a new window, or multiple tabs can be combined into one window.
• The new sandbox feature allows every tab to run independently from the other tabs, so if one site crashes it won’t take anything else down, and can confine “bad” sites to just their sandbox (instead of giving them access to your whole machine as in some browsers made in the Northwest of the USA).
• Activating the Incognito mode will prevent any pages you visit from showing up in your history.
• Chrome has improved warnings for suspected phishing sites, malware, etc.
• By clicking the star icon next to the address of a website, it is turned into a bookmark.
• It features Google Gears integrated in the browser.
• The Javascript engine is one of the fastest available today.
• Chrome is multi-threaded. Not only does this mean that one looping JavaScript will no longer tie up your whole browser, it simplifies memory management (since the separate process can be closed, and release all used memory), and can make use of multiple processors.
• Google continually updates a list of harmful sites, that Chrome uses to warn the user.

After all these benefits, there are some negatives:

• I couldn’t run the Chrome browser out of the box. Whenever I started it, it would give me “The application failed to initialize properly (0xc0000005). Click on OK to terminate the application.”. A bit of Googling taught me that Symantec doesn’t like the sandbox option of Chrome. If you add –no-sandbox to the shortcut used to launch Chrome, all is well (except you’re not using the sandbox feature).
• Limited plugin availability. Since the browser is pretty new, there aren’t a lot of third party, or even first party, add-ons, as opposed to Firefox.
• The end user license. Although Google’s motto is “Do no evil”, some of the wording in the EULA suggests that Google has rights to do anything it wants with whatever you enter through the browser. This sounds like Adobe’s EULA for Photoshop Express, and hopefully Google will revise the license to be more respective of the user’s ownership.
• Beta. I know Google has a history of releasing beta products (I think GMail just recently left beta status), but this time, the playing field is different. This is the frontline of the battle against intrusions, this is where the new malware tries to enter your computer. If there is a hole in Chrome, the bad guys will exploit it - especially since Google is a pretty high-profile target.
• Fear of lock-in. Soon you’ll be using GMail, Google Docs, Google Calendar, Google Spreadsheets, etc., all through your Google browser… One company to rule them all?

It will be interesting to see where Google takes Chrome, and if acceptance is going to be as high, or even higher, as Firefox.

If you want to try it, go to Google Chrome and download your copy.

I ran into a problem with Outlook the other day. Someone sent me a message, that was a forwarded message from someone else. Only, the forwarded message was attached, instead of quoted. And Outlook refused to open the message. Double-click, Right-click & Open, Right-click & Save, nothing worked (although Save gave me a beautiful .msg file - that Outlook refused to open).

After searching the Internet for a couple of days, seeing all kinds of references to security levels and warning messages (that I didn’t get - Outlook didn’t give a peep hen trying to open the message), I gave up - I only get one or two attached messages a month, and most of them are jokes.

It got annoying however when I decided to use the GTD Outlook Plug-in. In this plug-in, you have the capability to attach several messages to a Task. The message that initiated the Task is quoted in the task description, and subsequent messages are attached. I couldn’t open these attachments, and to make things worse, the GTD Plugin moved the messages that I attached to an undisclosed location, so I couldn’t find these messages anymore!

So, back to searching the Internets. I finally came across this message on Tutorials Win. It described a similar problem with Outlook 2007 (I’m still using 2003), and said that Google Desktop was to blame. That made sense: a couple of days ago Windows Vista informed that Google Desktop had unexpectedly quit. The forum post suggested disabling the indexing of Outlook, but for me, the only thing that worked was completely uninstalling Google Desktop.

Everything works fine now, I can access my attached email messages again. I’m sure I’ll miss Google Desktop, though…