Linked by Thom Holwerda on Tue 23rd Mar 2010 16:26 UTC
Permalink for comment 415029
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2005-10-19
can someone just comment on this?
"This also happens to be the reason why Opera Mini may be approved where other browsers weren't: since no code is being interpreted (it's all done server-side),"
Does this mean that the whole HTML interpretation and rendering is performed on the server side and the client app is nothing but an image viewer (to say it that way)? I couldn't believe that this would be faster than Safari which runs natively.
Adrian
Yes, that's correct. And you're right in some situations, it could actually be a whole lot slower, depending on how it's implemented.
If you're looking at a fairly static page, like news pages, then Opera will rip along (which is probably why they selected a news page for their demo).
If on the other hand you looking at a dynamic javascript/JQuery heavy page, like Facebook or online booking forms etc. then this will run like crap, (unless they have built in a local js engine as well).