Speed, security, open source. How Google has put these three in-line with each other is a bit beyond me, but my limited test run with Chrome shows *significant* speed increases, so I can safely say that I’ll play with it a bit.
Hopefully, I’ll be able to write about it’s best, and worst, features. Although, the idea of a browser’s performance moving me to write is a bit, well… disconcerting. But those are the breaks, right?
Anyhoo, the point of my posting anything regarding a browser is because of two things: (1) It’s a Google product (Hello! If this thing hits big and I ignored it, I’d look a bit ‘steewpid,’ to say the least.), and (2) Rendering concerns.
Google Chrome uses the same open source rendering engine as Apple’s Safari browser (WebKit), so your landing pages and sites should appear in Google Chrome as they do in Apple Safari. The way users interact with ads and sites should be similar as well.
Ensuring that your site renders correctly in Safari is a good indicator that GChrome will navigate your site just fine, but I recommend trying it out to be sure. If GChrome takes off (and I’ve very little reason to believe that it won’t) and you haven’t prepared for it, you’ll only be cutting off your nose to spite your face, in essence.
Thanks for dropping by and please leave comments of any kind regarding GChrome – it should be interesting to watch unfold.