The problem is that most of the world is not going to be using these powerful phones, and in the parts of the world where you can use them, operators are already killing unlimited data plans.
You are living in a dream world if you think compression is going away any time soon.
Trolling much? They aren't hijacking anything. Opera Mini is a thin client (which lets it run on just about any phone, including old and crappy ones), so they have no choice but to pass everything through the rendering engine on their servers.
What's wrong is that one feature gets one score, and another feature gets a much higher score. Scores are not based on the number of supported features, but on higher scores for certain features.
More than 1/3 of Opera's revenue is from the desktop browser. It's simply false to claim that it exists on the basis of mobile browsers (superb or not).
A random number like that is pretty useless. Opera has dynamic handling of RAM, so if you have a lot of it, it will use more. If you have less, it will use less.
> Although Opera is positioned itself as standard compliant, it has many issues with javascript.
I would have to disagree. Some people keep claiming that, but they can never seem to provide any evidence that Opera has more problems than other browsers.
Why should people have to understand URLs? Do most people understand how the engine of a car works? No. They just want to get from A to B. Most people don't care.
Comparing this to "young people don't understand words" is quite silly. Printed words are important. The message is important. And in fact, language is constantly being simplified, and has been simplified throughout history. Just like the address bar in Opera is now simplified.
That site isn't very useful since it only reflects what the author thinks is important. It doesn't show actual standards compliance. He chooses tests and assigns scores according to his own priorities. So it's misleading to call it "html5test."
It's a good codec. But as you can see, the specification was clearly not finished. So On2 sold a codec package that wasn't very polished. Doesn't mean it wasn't worth the money. It just means that polish needs to be applied, and now that it's open, it will.
On2 does not have the resources of Google and the entire internet at their disposal. Even the x264 developer pointed out that the VP8 spec was clearly unfinished.
The opera.com entry addresses that update. Look at the WebM FAQ: They have a separate branch for possible improvements for inclusion on the main branch.
He's suggesting a way to overcome design problems on a site.