Chrome: Back to Firefox

Google chrome FAIL! Oh noes
Creative Commons License photo credit: ronin691

After a day of using Google Chrome, I’ve gone back to using Firefox 3. My biggest complaint with Chrome is the lack of extensions (although it has been noted that these could appear in future). I find it much harder to do my job without Firebug, Web Developer Toolbar, et al.

I was perturbed by Google’s EULA for the browser, giving Google potential rights to everything posted via the browser, however they have since modified this to alleviate users’ fears.

I’ve also been put off by a couple of issues I’ve read about/discovered:

  • A flaw in the version of the WebKit browser engine Chrome uses allows an attacker to use a Java carpet-bombing attack, whereby a user can be tricked into launching an executable Java file.
  • Typing ‘:%’ into Chrome’s omnibar crashes the app hard, taking all tabs down with it. So much for tab process isolation!

However, I love the V8 Javascript engine:

It achieves great performance by compiling JavaScript to native machine code, rather than to a bytecode. Thus, JavaScript applications will run at the speed of a compiled binary.

37
Creative Commons License photo credit: themaxsons

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google
  • StumbleUpon
  • Technorati
  • Pownce
  • TwitThis

Tags: , , ,

Leave a Reply

Creative Commons Attribution-NonCommercial-ShareAlike 2.0 UK: England & Wales
Creative Commons Attribution-NonCommercial-ShareAlike 2.0 UK: England & Wales