Why I Don't Care About Opera | August 31, 2005
I don’t want to be the kind of person that sits on the fringes of a birthday party, bitching about the host, but I really hate Opera.
Now before I start, I just want to explain something. I really wanted to like Opera, I really did. When I first became aware of Opera in late 2000, Firefox wasn’t even a twinkle in its fathers eye. Opera was being billed as a fast, reliable and standards compliant browser, possibly even an IE killer. What developer wouldn’t be supportive.
And yet, Opera never lived up to the promise. In a time when the web standards movement was in its infancy, Opera 4 was without doubt more advanced that both IE4 and Netscape 4. However since then, the move to web standards seems to have out paced Opera development at every step.
I started developing standards based sites around the same time that IE5.2/Mac came out. At the time, this was the most standards compliant browser available, and the first browser to really show that CSS based layout was possible.
Opera 5 was supposed to be standards compliant, but it felt very buggy by comparison. Macromedia used the Opera engine on Dreamweaver for the “Design View” on OS X. If you’ve never used the design view in Dreamweaver 4, it was really bad, to the point of being unusable for CSS based layouts. Is it any wonder why people were slow to take up CSS development when CSS layouts don’t even work in the most popular authoring tool. Im not blaming this totally on Opera, as I believe the Windows rendering was pretty bad as well. However it didn’t make me feel particularly warm to Opera.
Opera seems to have had a major update at least every 12 months. Operas 5 came and went, as did Opera 6 and Opera 7. All were slight improvements, but all still had major CSS bugs. If you used a standards based approach to your coding, things just didn’t work as they should. More annoyingly was the consistency of things breaking. Fix something in Opera 6 and it would break in Opera 7. Fix it in Opera 7 and it would break in Opera 6.
People are notoriously slow at upgrading their software, and browsers upgrades are no different. Due to the regularity of Opera updates, the developer is left with a mass of buggy browser versions to contend with. Once Opera 5, 6 and 7 have been retired, I’ll be a lot happier.
Opera started to become the bane of my web development life. Layouts would work “out of the box” in Firefox and Safari. They would work pretty well in Netscape, albeit it with the odd tweak here and there. Internet Explorer is a pretty buggy browser, but because of its market share it is an important and well known browser. As such, bugs get found, documented and often fixes or workarounds are discovered. No such luck with Opera.
At first I started to care about Opera. But as each successive site I built failed in Opera, I started to care less and less. At the start I tried to find workarounds, these days I don’t bother. Now days I expect CSS based sites not to work properly in Opera, and it rarely disappoints me. As such, Opera is my nominated “to fail” browser. If I have to choose between something breaking in one browser, but working in everything else, I choose Opera.
For a web browser that is 10 years old, up to version 8, and developed by one of the inventors of CSS, I had honestly expected more. Opera 8 is now finally a reasonable browser. It still has odd CSS bugs, but nowhere near as many as it’s ancestors. Unfortunately I’ve been let down by Opera so many times, I no longer care.
So happy 10th birthday Opera, but I really couldn’t care less if you made it to eleven.
Posted at August 31, 2005 9:14 AM
Drew said on August 31, 2005 9:47 AM
I think I’m right in saying that Opera wasn’t used as the rendering engine for Dreamweaver until DW MX.
The only good thing I have to say for Opera browsers is for the mobile editions. Opera on my S60 phone is about the best mobile browser I’ve come across. But on the desktop? Yeah, forget it.