It is bizarre to make each page reload when you restore the browser from minimised, or to make pages reload when you hit back.

It is beyond bizarre and well into the realms of dementia when this behaviour is programmed into a mobile device that uses slow and unreliable GPRS coverage.

What should be the simple act of switching back to the browser to a have a quick look at a page you already opened can easily take 5 minutes, or never if the GPRS connection has since been lost.

Opera’s desktop browsers have always made intelligent use of caching, so I’m sure they’ll be able to get that right no problem.

I’ll be there with my doolah to get hold of Opera’s browser if they do release it for Android.

And Opera Mobile (for WinMo) works as well (I just tried), but gets booted by google whenever a document finishes loading, saying “Browser does not support web word-processing (even though you can edit docs, while the page is loading).

“What makes you think Opera can make a mobile browser that properly supports Google Docs when their desktop version does not?”

.

What makes you think the desktop version can’t?

.

As far as I know, the reason for problems with Google Docs is that Google is specifically blocking Opera in some way. If Google would just stop blocking Opera, it would have worked fine.

.

“Not to mention how far behind the competition they are with JavaScript performance.”

.

Nonsense. Opera is very fast at JS. The only thing it doesn’t win at is a bunch of artificial JS benchmarks that don’t actually test relevant JS or real world performance. They only test whether the JS engine is using JIT and stuff like that. Opera’s new JS engine will support JIT and all that nonsense, but it won’t be faster on real sites because JS is not the main bottleneck.

“What makes you think Opera can make a mobile browser that properly supports Google Docs when their desktop version does not?”

What makes you think the desktop version can’t?

As far as I know, the reason for problems with Google Docs is that Google is specifically blocking Opera in some way. If Google would just stop blocking Opera, it would have worked fine.

“Not to mention how far behind the competition they are with JavaScript performance.”

Nonsense. Opera is very fast at JS. The only thing it doesn’t win at is a bunch of artificial JS benchmarks that don’t actually test relevant JS or real world performance. They only test whether the JS engine is using JIT and stuff like that. Opera’s new JS engine will support JIT and all that nonsense, but it won’t be faster on real sites because JS is not the main bottleneck.

I started using Steel as my default web browser within a month of getting my G1, and I’ve rarely ever looked back. It’s faster and more intuitive than either Opera Mini or the revamped Cupcake original.

“passes web data through Opera’s servers” – how would this work for countries that filter web content? Wouldn’t they end up blocking Opera’s servers?
—————–
Opera Tubro can be turned off in any case. But then you’re stuck at normal speed. D:

But what if opera doesnt handle tis too? I would love to try out another browsers

Yes it loads, but there are so many bugs it’s essentially unusable. Just try adding a line break to a document and prepare for frustration.

Not to mention how far behind the competition they are with JavaScript performance. Opera is a nice product in many respects, but Web 2.0 is not one of them.

@johnkzin I’m with Eric on this one. Why would you want the “real web” on your mobile browser? Through my Android browser, I use Google Reader and Google Tasks just fine. They create “watered down versions” for phones because phones can’t render the same things computers with big engines and 22″ monitors can.

All Opera really has to do to compete is fix the mini UI.