Today’s comic features Opera’s viking doing some nasty, brutal stuff. Because if a public community representative of Opera acts out of line, and the company doesn’t call them on it, they might as well be endorsing it. Luke Wroblewski also stars as the stand-in for well-meaning folk who are trying make peace at the expense of correcting bad behavior.

Buckle up.

I’m going to throw myself on the grenade and be the curmudgeon.

You don’t have to like what I’m about to say, but I think you need to read it.

We are, as a community, allowing ourselves to be abused. We’re Kevin Bacon in Animal House, bent over in our underwear and thanking someone for beating us. And, like any sadist with a free pass, they’re continuing to hit us again, and again, and again.

I get it. It’s the holidays. We’re stressed out by end-of-year deadlines, driving on icy roads and getting our Christmas shopping completed and hoping that at the end of the day we can kick back an egg-nog and just be merry. We don’t want the stress of confronting and condemning bad behavior, so we’re trying our damnedest to shrug it off.

Additionally, most of us want to be liked. And we want our friends to like each other. Whether it’s in our neighborhoods, in our Facebook profiles, or in our professional circles we just want people to be friendly and think highly of one another, but especially us. So when a flare-up starts between two peers we’d rather put our fingers in our ears and hum the Benny Hill theme song than owe up to the fact that there’s a problem.

But I’m here to be the bearer of bad news: there is a problem. Not only that, we’re responsible for it.

When I was growing up, my mother made it clear that certain behavior was not acceptable. Among other rules of childhood, I couldn’t go about tossing insults at people. Not my parents. Not my siblings and not friends. Heck, I was expected to maintain at least some decorum around the kids I disliked.

Going outside the bounds of socially acceptable behavior carried with it a penalty. Maybe soap in the mouth, or a spanking, or being grounded in my room, or at the bare minimum no desert after dinner. It was unpleasant. I was a pretty big crybaby, so any sort of punishment or chastising resulted in a waterfall of tears and a sniffling cry that would last for hours. I guarantee my mother hated having to deal with it. She probably would have enjoyed her evenings much more pretending I didn’t doing anything wrong, instead of listening to me cry and sniffle in my room as she desperately tried to read a book in peace.

But she did it anyway. As a result, I learned the difference between right and wrong and stopped doing the bad behavior. It didn’t mean that I stopped thinking ill of kids I disliked, or devising a choice insult for my brother when he provoked my ire. But it did mean I knew it was unacceptable to act on those thoughts, and it made me consider my words before I said them. If, after a good hard think I decided it was worth provoking my mother’s wrath, I’d still take the risk of insulting someone.

I did, however, think first.

In a pattern that goes back probably for quite some time but for certain seems to have flared up this week we’ve been permitting ourselves to be subject to bad behavior. We’d rather read our books in peace, so we are ignoring the misdeeds of an entitled few in the hopes that it will all go away.

And it’s not going away.

There’s literally thousands of amazing, talented developers and designers currently involved in making the Web a better place. A whole lot of them are like me, working hard for a very modest living in a small design firm that doesn’t get awards or fancy big-name clients. A great many also work as embedded Web people in a large corporation or other entity, thanklessly fighting the ignorance or misinformation of their bosses and co-workers while trying to apply their awesome skills to making their corporate site a better, slicker place to visit.

Then there’s the superstars, Web folk that work as community representatives and star developers for the big Web companies that take leadership roles (by fiat or by standards) in developing and proselytizing the advancement of the very technologies we use to make awesome Web stuff.

These people don’t just speak at conferences, they speak at dozens of conferences. They don’t just make cool web projects. They make amazing, cutting-edge projects that push forward the meaning of “good Web design”. They talk a lot about community participation and self-learning and being involved.

They’re intelligent, creative and successful people.

Sometimes, they can be utter dicks.

Anyone can be a jerk. From the drug-addled homeless man currently shooting up in the alley down the street from my office to the richest men in the world. Every person is capable of forgetting those lessons in basic decency that their parents (hopefully) taught them as children and slip up from time to time.

When it happens, it’s usually considered acceptable to say “Dude. No.”

The worse the bad behavior, usually the more stringent the chastisement should be. Action. Consequence. It’s a no-brainer, right?

But what happens when thought leaders, community representatives of important companies in the industry, and superstar talents start to repeatedly engage in or endorse bad behavior? It usually goes something like this.

1. The superstar does something socially unacceptable. Like refer to a recent article by the owner of a small design firm as drug-enduced bullshit. (original was deleted, here’s a retweet).
2. Individuals call the superstar on the behavior, noting how unacceptable an action it is. Especially for a community representative of a major player in our industry (although, really, it’s just unacceptable period).
3. The superstar sort of apologizes. Usually in the vein of “I’m sorry for using strong language” or “I’m sorry you got upset”.
4. The individuals (rightfully) insist that’s not an acceptable response, and demand a genuine, public apology.
5. The superstar does so.
6. Supporters of the superstar retaliate by calling the original individuals the curmudgeons in this situation. They in essence defend the bad behavior by shaming them for “bullying” the superstar, say the “crap” they’re saying is undeserved.
7. The rest of the community, straining to retain a smile, do everything in their power to bury the “firestorm” under a (likely well meant) pile of hugs and cookies universally handed out to everyone involved, including those that defended the bad action and the superstar that did it in the first place. All are pardoned, nobody is wrong.
8. The superstar states how tired they are of the drama… seemingly ignoring the fact that it was their own behavior that caused it.

This is all sorts of messed up. Nobody’s learned a lesson, because as a community we’re too concerned about “drama” that we’ll do anything to quash it instead of uniting as a community to call down the person who started the drama with their attack in the first place. We’re sending such a mixed message of supporting the peace or the person without collectively condemning the behavior.

Anyone who ever raised a kid or was a kid knows exactly where that will lead. To more bad behavior.

I’m not calling for punishment. But the launch of a pro-community “make the web better” website (which I will not be linking or mentioning by name for reasons I’ll make clear below) should have been a source of joy in the holiday season. Instead, two individuals tied to that effort have engaged in either passive/aggressive sniping or outright insulting of individuals and their efforts in this week alone. And according to people in the know, this isn’t the first time for some of those involved. And what kills me, what hurts me is how highly I thought of these people prior to now. But how can I promote the work of people who engage in socially abusive bad behavior?

I can’t. No matter how much I agree with the message of their product, I cannot in good conscience promote their goods and services when they’re behaving in a fashion that I know to be wrong. And as near as I can tell, they’re not sorry for how they’ve behaved. They’re simply sorry they were called on it.

The only way we’re going to improve as a community is to grow up and realize we can’t hide everything under soothing hugs and cookies. People messed up. Worse yet, people who are well known and respected representing companies with power or social clout messed up. If they are protected for their behavior, they will continue to abuse us, the community. And many of us will, over time, mimic that behavior in a misguided attempt to become as successful as they are.

Shame on you, Divya. Shame on you, Paul. You’re grown adults. You know better.

Next time you want to blame the drama, stop for a moment and think about who actually started it.

And to the rest of you, I’m sorry. I don’t want a cookie. I want it made clear that this behavior should never have happened, and can’t be allowed to keep occurring.

Happy holidays.

I’m actually shocked by the IE9 beta that was released today. It’s got a slick, minimal interface that is such a radical departure from what I’m accustomed to from Internet Explorer that I’m left speechless. It’s also fast. Surprisingly so.

These two facts are just a small portion of what IE9 brings to the table. Improved CSS3 support. HTML5 elements are now supported, including beautiful elements like <video>, <audio> and and the sexy girl on the block: <canvas>.

I could wax eloquent, but I prefer to direct your attention to smarter people saying the same thing with better word choices, like Rey Bango. Go check his blog post on the topic right now.

One beef people are pulling out to disparage the new release with is IE9′s lack of support on XP. I get the gist of where they’re coming from: the less operating systems IE9 is supported on, the harder it’ll get to make hardliners upgrade off IE6 or 7. But the fact is, XP is old. Really old. You don’t see people complaining because Safari 5 isn’t supported on Mac OS X 10.4, do you? I’m sure the reason Apple didn’t do backwards support is the reason Microsoft did what they’re doing. Both are in the habit of selling OSes. And if you’re not calling Apple down for that behavior, it’s more than a little hypocritical to do the same to Microsoft.

(Frankly, If you’re using a beast of an old OS, I suggest you go to other vendors like Mozilla and Opera for your modern web experience. Or upgrade your OS. Which path you pick is probably based on your pocketbook.)

Speaking of which, I’m not an IE user. It’s catching up, but it hasn’t surpassed my experience with other browsers like Firefox or Chrome (although FF is getting chunky in a way that alarms me, but I believe version 4 is going to correct that). But it’s improving by leaps and bounds, and I think we should acknowledge the effort Microsoft is putting into burying the mistakes of their past.

If you’d like to check IE9 out, you can download the beta here.

I hope you’re able to follow the metaphor I’ve created, as I don’t think I can devise another way to repeat what I just said above.

Frequent readers may be aware of the fact that I have not been too kind to Opera in the past. Typically, these tussles have dealt with how they’ve handled conflicts with certain competitors. Today,  it’s a different story.

What Matters With Mobile: Speed

I own an iPhone, a device that comes pre-installed with Mobile Safari. Safari is a great modern browser that renders most (non-Flash) websites beautifully and accurately. And when I’ve got a decently strong connection, it even does it in a time-frame approaching (but not reaching) quickly.

The fact is however that my phone’s provider is AT&T. And when I’m at home, my WiFi access is through Comcast. Despite their many bold claims and lovely commercials stating otherwise, neither vendor provides what I’m going to refer to as a fast connection. Quite the opposite, I’m positive that there are several times in any given day where a 28.8k modem would more quickly deliver me the information I am seeking to consume.

Tell me, why as a society is it acceptable to charge people for a speed that they might, but usually won’t, receive from any given service, rather than the speed that they actually are receiving?

Regardless, these modern day robber barons aren’t making my service any better anytime sooner, so experiencing the web through Safari on my iPhone is similar to experiencing a milkshake through one of those really tiny coffee stirring straws. Yes, sooner or later you’ll get the shake, but it’s not exactly at a speed that’s enjoyable.

This is where Opera Mini comes in. Yes, it’s a less-capable browser in the rendering sense. But if I want to wait for a minute or longer per page,  I can certainly do so for my rounded corners. Usually when I’m on a mobile browser, I want data quickly. Very quickly. So Opera Mini serves me just fine. Better than fine, in fact. It’s very fast. Which makes surfing the web effortless again. Which I dare say is how it is supposed to feel.

Addendum: Privacy & Security

A few days back, I made the following pro-Mini tweet: “Speed matters. Especially on mobile. And that is exactly why I’m using Opera Mini more than Safari, despite the rendering deficiencies.”

Ben Adida offered the following question as a counter: “Does privacy matter? Cause Opera Mini proxies all of your connections, even SSL, via its servers.” It’s a valid question, especially considering his expertise in the field of privacy and security. Not being an expert on how Opera does things, I poked at both Bruce Lawson and Molly Holzschlag, both Opera employees.

Both of them said “If you don’t trust us (Opera), then don’t use the service,” and then each followed up with more details.

Molly backed up the security conversation with this gem: “Regarding proxy serving in Opera Mini? We are a public company in Norway, which has some of the most stringent privacy rules.”  as well as the very honest tweet: “As such if you cannot trust based on the integrity of a product or its company, no matter who, then don’t use that product!”

Well said.

Bruce gave us reasons to trust Opera with two security-related links. First, he indicated that Opera Mini is actually more secure on public WiFi than other browsers (with this link to back his claim) as well as linking to a post about how well Opera scored with security according to Symantec (here’s the abridged version: very well.)

So is Opera Mini fast? Yes. Is it secure? Yes.

That’ll do, moose. That’ll do.

Today’s comic is one of those little jabs at everyone’s favorite European browser maker. I’ve got issues with Opera that this comic makes light of (while wishing squirrel snogger and Opera employee Bruce Lawson a belated happy birthday). Yes, Opera is a far smoother experience for modern web features than Internet Explorer. That’s not in question. But I’m getting a bit exhausted by the relatively slow adoption speed of CSS3 features by the browser in comparison to the increasingly popular Firefox and Webkit-based browsers.

Rounded corners are, admittedly, largely a non-issue. If visitors using Opera get square corners in a design, I’ve taken steps to ensure it’s at least a good looking square design. It’s an example, though, of a slew of features that Opera’s failing to keep pace with. Due to this lack of universal browser support (in the modern browsers, at least), It is hard for me to sell adoption of these designs to clients when roughly 1% of a customer’s visitors are getting a bad experience as a result.

Take for example, Jonathan Snook’s text-rotation tutorial. It provides a way (via filters) to get even IE to come to the ballgame with producing vertically-oriented text. Everyone, except Opera, can play with this toy. Even if IE couldn’t, thanks to conditional comments, I could provide a fallback solution for that browser. But as Opera lacks such (and I’m not recommending they adopt conditional comments), there’s no way with just CSS to provide an acceptable fallback that makes the browser not create something hideous with the text out of place. (I’ve concocted a JS-based solution, but I don’t want to have to rely on that to get CSS to work).

Opera’s not alone in the modern browser category in being the last to adopt a given feature (I’m looking at you, Firefox), but there’s definitely a lot of seemingly basic CSS3 techniques that the browser’s fallen behind on. Just because you can wait on adoption, gents, doesn’t mean you need to do so. The future isn’t coming any more slowly, and designers will have to jury rig solutions that would be solved much more cleanly with CSS if you’d keep pace.

Or, even worse, there could be more situations such as when I’ve suggested to some people who’s sites don’t have any notable Opera traffic that they just not sweat Opera support at all. With as small a market base as you have, it’d serve you better to keep pace (rather than not sweat the details, as Microsoft can afford due to its market share).

Curious about a browser’s support for various features? Check out When Can I Use.

I also saw Star Trek. It was good. It was better than good. Go watch it, you’ll love it. I promise.

As it stands, I’ll take a swing or two in his place. First, let me direct you to today’s comic featuring Andy Clarke, wherein a couple of cheap shots are made at Opera’s expense. Then, continue reading.

First, I’m aware that browser usage statistics are like a dark art, much akin to necromancy and astrology, where accuracy isn’t really achievable. But the fact is (and take a look at Wikipedia’s page on the topic) that Opera according to some of these browser usage sources does in fact have less users than Netscape.

That’s right, there’s still people using Netscape. How scary is that? I wonder if they think grunge is alive and watch reruns of Family Matters while downloading websites on 14kbps modems. And just to reiterate, there’s more of these people (according to some sources) than there are people using Opera.

Beyond that, Google Chrome is the new hot browser in town and has already exceeded Opera’s user base in less than a year. That’s right, less than a year.

Look, I’m not saying it’s the number of users that count. After all, IE6 is utter rubbish and it’s still being used by too many people out there. What I am saying is that instead of wasting your company’s public image whining about the fact that Microsoft is doing us all a favor and forcing IE8 updates over their update system, you could be spending time looking at your own browser and figuring out why among other things a browser that has been dragged along for a decade by AOL then finally shot in the head (aka, Netscape) still has more users than your product.

Instead of making absurd suggestions that your competition serve your product via their update service, maybe you could look at Google Chrome and devise how it so rapidly out-paced you in such a short period of time?

Microsoft’s browser, even its newest version, isn’t even close to the coolest browser on the market. I don’t like Internet Explorer, and I only use it to check website compatibility in my job. But I don’t use Opera either, and that’s because (among other reasons) it has thus far convinced me (and the rest of the world) that it’s not worth the effort of installing and using rather than Firefox, or Safari, or the other web standards-compliant browsers on the market. It’s enough to make me wonder why we consider Opera part of the Big Four (now the Big Five). At this rate, with even terminated browsers giving Opera a run for the money, should we expand that name to the Big Six?

Is Opera a good browser? Yes. If that’s not the reason that it’s being ignored, than what is? Perhaps a lack of add-on support. I’ve always felt that Opera’s too busy telling people how to surf the web, and not spending enough time figuring out the features people want. Firefox isn’t popular on accident.

But I’ll tell you the number one reason why I don’t use Opera. It’s because of the company’s public behavior with their legal actions and petulant whining. The rank-and-file employees are talented people creating a worthwhile (albeit, not standout) product. But the big shots on top cost the company their credibility every time they make a cheap, transparently spiteful shot at the current market leader.

And lest I let the others off the hook, shame on Mozilla and Google for getting involved with the EU nonsense. Focus on your products, not on begging the government to get people to install your browsers for you.

As I was crafting a response, I discovered that I had more to say on the topic than could be rationally contained in a simple comment.

First, some facts: I don’t dislike Opera. I dislike hypocrisy. Also, I don’t like Internet Explorer. I hate Internet Explorer, and I would prefer to see Microsoft adhere to modern web standards with the same fervor as the other major browser makers.

However, the responses to my earlier posts made by Opera employees and by others on behalf of the browser maker, amount to the following two statements.

1. Microsoft needs to adhere to Mr. Lie’s list of rules they should play by because Microsoft is a monopoly. Opera does not need to do this because it is not.

2. Opera is justified in delaying implementations of “new” features because they’re focusing on backwards compatibility and not breaking the web.

Each is interesting, but ultimately unconvincing.

First, I don’t believe that implementing web standards and new site features is solely the responsibility of a company that is a monopoly. In his well publicized list of rules for Microsoft, Mr. Lie agrees with me. I’ve already quoted the fifth point (relating to adding a new standards-related feature to a browser if two major browsers have already implemented it), and have pointed out useful features that at least two browsers have implemented that aren’t live yet on Opera. I want to emphasize where Mr. Lie states these rules aren’t just for Opera:

“Microsoft will surely claim that it’s impossible for them to develop a browser that complies with the proposed requirements. However, other browsers have played by these rules for years. If Microsoft can’t live up to the standards of the web, I suggest they leave the browser business.”

His assertions are twofold, first that other browser makers do play by these rules (including Opera I presume, which exclusively makes a browser), and that failure to adhere by these rules is enough reason for a company to leave the browser business.

I agree with him completely. I find it comical that some of Opera’s employees apparently do not, and have yet to hear a compelling argument as to why they should be disregarding their CTO’s wisdom. This ties directly into point #2, which is that implementation of new features must be delayed as a necessary sacrifice to maintain backwards compatibility and not break the old web.

Backwards compatibility with the soccer mom-built sites of the world is the same boogeyman that Microsoft has been waving on a flagpole since at least Internet Explorer 6. The world of web developers have yet to give Microsoft any mercy for that, and often cry for blood when feature implementation or standards compatibility is sacrificed on that altar (such as the well documented IE8 meta-tag explosion). I’ve yet to hear a compelling argument as to why any smaller browser maker can justify their own delays at implementing “new” stuff with the same smoke and mirrors and not deserve the same treatment.

In the end, the simple fact is this: I expect better of Opera. I expect them to be better than Microsoft. This means I’m not going to accept Opera using the same excuses as Microsoft, and somehow get away with it due to their size.

So, chop chop. Back to the grindstone, boys.

As much as I’ve teased Opera in this site’s comics, I really have to hand it to them. Recently Opera revealed a website that’s devoted to the very concept of web education: the Opera Web Standards Curriculum. It’s got about twenty articles devoted to web design and development, and there’s the promise of more on the way. These aren’t quickly written tutorial blog posts, but polished well written articles that are meant to give a good foundation for anyone interested in web standards and development.

The majority of the articles contained there thus far are mostly about history of the web, the concepts of web standards, basic web design theory, and HTML. Which I think is brilliant, since this is the area that most online tutorial sites skip right past, and thus there’s the most immediate need for. Discussions of things like CSS I’m sure are in the near future, and I’m excited to see their take on it.

1. He left a comment. Which I love. Feedback of any sort is appreciated, especially when it includes the phrase “funny comic”.

2. He defended his company’s product’s implementations of standards by pointing out that one of the three CSS properties I mentioned is in 9.5 (which is now launched), one is only experimentally implemented, and the third is as he puts it “not in a stable spec”. I’ll give him the first two, but I don’t think word-wrap is unstable enough to justify not implementing it.

3. Lastly, he threatened to attack me with the SVGorilla.

The idea of a smoothly scaling primate collided with my recent CSS3 rgba colors experimentation in my head, and spawned this week’s comic.

Opera’s been doing a fine job with their browser, and 9.5 is actually pretty slick. Will I use it day to day? No. It’s feature set does not offer enough to draw me away from Firefox, which is officially launching version 3.0 in mere hours. If addons became a big thing with Opera, I think it’d have a fighting chance in sucking me in, though. As a rule, I prefer browsers made by browser software companies, not operating system software companies.

That said… although the properties I’ve mentioned earlier (word-wrap, border-radius, and outline-offset, aren’t exactly going to see a lot of use by me. However, CSS3 rgba colors? I’m all over that. I especially enjoy the ability to set an element’s opacity without it affecting all of its children. I don’t think it was a good call for Opera to skip adding this into 9.5, as it means it may be a while yet before we see it in an official Opera release.

Well, on the plus side, it let me escape the vicious SVGorilla.

Although I’ve been running the beta (then later the release candidates) for some time now, I’m excited for the upcoming official release of Firefox 3 tomorrow. Although I hadn’t planned out a release party like Mozilla has encouraged as part of their Download Day 2008 event, I’ll definitely be upgrading to the release version to help with their “most downloads in one day” goal.

In related news, while I’ve made it clear how much I dislike their tendancy to swing at IE without checking if their own zipper is up, I am also glad to see Opera 9.5 has been officially released, bringing with it a slick upgraded interface, more speed, and overall better standards support (but still no CSS3 rgba color support yet.) Between those two and Safari, a lot more CSS3 and other standards-related features are becoming available in 2008.

Now if only Microsoft would get off it’s lazy rear and announce a general target for when they plan to release IE8. Preferably this year…

This week’s comic is not about Microsoft. The history of Internet Explorer’s many issues with standards compliance is well documented elsewhere, including various frustrations listed in this blog and in many of my posts over at Mindfly.

This week’s comic is about expecting a certain standard from someone when you are not living up to those standards yourself. In this case, of course, I’m discussing web standards and the big flap they cause in the development/design world due to the various browsers’ speeds at implementing them.

If you’re a designer, and you’ve ever had to make a website trying to find out how to make a website look correct in Internet Explorer, than you understand how important web standards are. It saves us time, which means it saves businesses money, and ultimately all the happy little people surfing the web get to see their favorite website about cute puppies the way that the site’s designer intended it.

So when someone says: “Hey, browser makers, get on board with styles already,” I’m going to be right there holding a sign and trying to pretend that protesting in the middle of winter in Seattle isn’t cold and demoralizing.

Everything in moderation, though. When Opera went to the European Commision to try to force another browser maker to change it’s feature set through legal actions, we start to muddy the line between “good activism” and “bad business behavior”. When Håkon Wium Lie, Opera’s CTO, then at several different points (including in this article/rant at The Register) outlines a very specific, detailed list of what Microsoft needs to do in order to be compliant to Opera’s view of a browser maker’s responsibility, things go from bad business to hypocrisy.

Why hypocrisy? Simple. Mr. Lie’s little list is incredibly specific, as expected of a programmer, and includes several points that must (his word) be adhered to. The one of most interest to me at the moment is the closing one:

“5. Commit to interoperability. It is important to ensure that Microsoft remains committed to supporting web standards, even beyond Acid2 and Acid3. If two or more major web browsers, in official shipping versions, add standards-related functionality that’s generally considered useful to the progress of the web, and described in a publicly available specification, Microsoft must add the same functionality.”

Is this a good idea? Why yes, yes it is! Nothing frustrates me more than finding a good CSS3 property (or CSS 2.1 property) that would solve a design issue I have with a website, only to discover that a couple of the leading browsers don’t have it, thereby making it of limited use. This is something I experience on a weekly basis (if not more frequently), and probably the largest source of frustration with my job.

However, Microsoft isn’t the only browser that needs to do this. After all, what good is it if only IE was keeping up with standards? Yes, it has the dominant share in browser usage, but there’s a good 25%-30% of users who are using other browsers like Firefox, Safari, and Opera. We wouldn’t want them suffering because their browsers aren’t keeping pace.

Generally, of the four browsers, IE is in fact the one that typically is behind the game. But while going through several CSS3 properties last week, I found myself looking at three that Opera was not yet using, but that were in use by at least two other browsers.

What’s that? Is Opera not living up to the standards it’s expecting of others? Why… that would be very hypocritical of them, wouldn’t it? They’d NEVER do that!

Well, as it turns out, yes they would.

The properties in question (and this isn’t a complete list, I’m sure, just one that came up from only an hour or so of looking) are as follows: border-radius, outline-offset, and word-wrap. The first two are implemented in Firefox and Safari. The last one is implemented in Firefox and (gasp!) Internet Explorer. All three are documented in publicly available specifications.

Opera can’t render any of them.

Now, granted, outline-offset will appear in Opera 9.5. As of yet, though, I’ve seen nary a peep about those other two, and I doubt that’ll change before 9.5 goes gold.

Frankly, Opera, you need to stop focusing on legal action against your competition. This kind of behavior is belittling, and ultimately serves as little more than a PR stunt as long as you’re failing to actually keep your own browser living up to the standards you’re yelling at others for failing to uphold.

We get it already. Microsoft sucks. Now stop poking the big dog with a stick and go grab a larger share of the market by showing everyone how cool Opera really is.