Posted by Richard

After this forum post by Ella in the WordPress.com forums, and Teck’s comment here on this blog, I was about ready to change the title of this post to “Google Chrome: NOT ON YOUR LIFE,” but with a little time going by (and taking the time to try it out), and a post by Matt Cutts (Googler) on his blog, one of the two – the Chrome end user license agreement (EULA) – thorns have been removed, or will be shortly according to Matt. (Note to Google: One size does not fit all!) The other one – the potential piece of malware installed with Chrome that Teck reported – is still a concern although it was not installed on my computer when I did the installation. During installation I told it not to send information on crashes and such back to Google, so perhaps Teck did not disable that at install. And there are other concerns as well including some apparent security issues. I’m not going to repeat the sloothing of others, but will include links to things I think you should be aware of.

This isn’t going to be an indepth review of features and such, but simply my observations from several hours of use over a couple days. I’ll start with general impressions and then move into how it functioned with WordPress.com and the stand-alone WordPress software from WordPress.org. At the end of this post, I will list some good sources of information if you wish to look further.

Do keep in mind: Chrome at the time I’m writing this is in Beta, which means it isn’t finished. Hopefully the issues will be taken care of by the time it reaches actual “ready for prime-time” release.

[Update 1: Warning! There have been a few more security holes uncovered and reported by Information Week, and the security issues are not something that will be caught by antivirus software or spy software, so don't expect them to keep you safe. Please read the article and be very careful until Google gets these issues resolved.]

Continue reading →