An attempt at using Opera
:: Tuesday, November 6th, 2007 @ 12:48:26 am
:: Tags: Computers

Well, I gave it a try. After being frustrated with the performance of FireFox on Mac OS X, I decided to give Opera 9.2 a try. I used it for about 2 weeks as my primary browser.
The reason I was driven to trying a new browser is that FireFox crashes on me regularly and is starting to feel bloated — at least, on Mac OS X.
When I installed Opera, I immediately noticed how fast and snappy everything is. I loved the built-in sync feature, too (I use Google Browser Sync on FireFox, but it doesn’t sync with Opera on my Blackberry). But in the end, compatibility issues forced me back to using FireFox.
Specifically, here’s what I had problems with in Opera:
- No keyboard shortcut to get to the search box. I had to use “g subject” on the address line instead of hitting a command key and typing in my search.
- Incompatibility with TextExpander, which I rely on heavily.
- General incompatibility with frequented web pages. Rich text editors in forum software didn’t work. Embedded YouTube videos worked inconsistently. Google Docs doesn’t work.
- Flaky cookie support. Sometimes, I would be logged out of things mysteriously.
- Inconsistent username / password field memory. I had to do a lot of typing when username and password fields weren’t remembered.
- Fewer add-ons.
It’s too bad, because I tried to like Opera. I guess I’ll try Safari 3 once I hear that the beta doesn’t screw up VLC. I’m too afraid to try it now.
When you upgrade to Leopard, you get Safari 3 as part of the deal. From what we’ve seen in development testing, Safari 2 to Safari 3 is almost as big a change as from IE6 to IE7.
I want to try Safari 3 as my primary browser, but need someone to port the PwdHash extension (Firefox and IE) to it first.
I like Safari 3, they fixed a bunch of long-standing bugs.
[...] An attempt at using Opera [...]
Although I rely on too many Firefox extensions to switch, the GreaseKit plugin for Safari does allow you to implement many Greasemonkey scripts on Safari, which greatly expands your options. It would be great to see browsers support a common standard for Javascript site plugins. I know Gmail is now offering an API of sorts for greasemonkey script developers. (Gmail 2.0 is still better on Firefox than Safari.)