![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
Back to Chrome
« previous entry | next entry »
18th Apr 09 | 06:51 pm
location: Hillel
mood: 
chipper
Now Playing: The Entertainer -- um, why?
Oh, shiny, shiny interface. Oh, Omnibox. On "Speed Dial" home screen. How I missed you.
I've switched back to Google Chrome, and this time, I think it's for good.
As I described so long ago, the main reason I switched away in the first place was lack of Flashblock. In addition, I was worried about trivial things like "security" and "speed."
Regarding security, I realize the master password is kind of silly for Chrome's user experience. And if I consistently lock my screen when I go away from my computer, it's not something I have to worry about. In terms of vulnerability to attacks, I think the results of pwn2own speak for themselves.
Regarding speed, those weird slow-downs I'd experienced seem to no longer be a problem, at least in Chrome 2.0 beta. Part of that might be that this version of Chrome has somehow been made EVEN FASTER in terms of Javascript execution, but I think the real answer lies below:
Chrome 2.0 has support for add-ons. And while everything's still very much in beta, some wonderful, wonderful souls (scroll to the bottom, to the "answer" by ChromeFreak) have taken to making a version of Flashblock. The interface is a bit clunky (Shift-F to whitelist a site; hunt down a cookie to remove it from the whitelist), but by-God, it works (for instructions on installing an extension in Chrome 2.0, click here).
So I'm rejoicing in the glory that is un-dockable tabs, Google Docs integration and sandboxed processes (ooh! Looks like they've added custom dictionary support!)
P.S. I swear, I *am* working on my Honors. I just implemented three chapters worth of corrections. So I'm taking a teeny break.
I've switched back to Google Chrome, and this time, I think it's for good.
As I described so long ago, the main reason I switched away in the first place was lack of Flashblock. In addition, I was worried about trivial things like "security" and "speed."
Regarding security, I realize the master password is kind of silly for Chrome's user experience. And if I consistently lock my screen when I go away from my computer, it's not something I have to worry about. In terms of vulnerability to attacks, I think the results of pwn2own speak for themselves.
Regarding speed, those weird slow-downs I'd experienced seem to no longer be a problem, at least in Chrome 2.0 beta. Part of that might be that this version of Chrome has somehow been made EVEN FASTER in terms of Javascript execution, but I think the real answer lies below:
Chrome 2.0 has support for add-ons. And while everything's still very much in beta, some wonderful, wonderful souls (scroll to the bottom, to the "answer" by ChromeFreak) have taken to making a version of Flashblock. The interface is a bit clunky (Shift-F to whitelist a site; hunt down a cookie to remove it from the whitelist), but by-God, it works (for instructions on installing an extension in Chrome 2.0, click here).
So I'm rejoicing in the glory that is un-dockable tabs, Google Docs integration and sandboxed processes (ooh! Looks like they've added custom dictionary support!)
P.S. I swear, I *am* working on my Honors. I just implemented three chapters worth of corrections. So I'm taking a teeny break.