[joe3789]

Originally Posted by joe3789

Sorry SuperFly ... lol . But I have to take some of what I said back. I took a look at the Iris Browser again, today. It's quite improved on the latest v.1.0.10, just released 5/5/2008. But it's still slow. It renders very nicely, though. The MSN homepage "dashboard" even transitions nicely, although MSN took a decade to download. I find a good test for these mobile browsers is to go the desktop version of Facebook. The original Facebook site is too heavy for Iris at this time (I get the following error: "Memory usage exceeds process memory limit!"), which is wierd (Opera has no problem with the desktop Facebook site IMO). Maybe it has something to do with WebKit. The iPhone Facebook site loads pretty well in it, though.

I got some more info yesterday from Torch about this browser.

"Hello Joe,

We are working on supporting Flash but it will not be free to
start. The Flash plugin carries a significant runtime fee. We hope
that will change someday. As for page loading, we are actually using
the Mobile IE network stack so our networking should be no slower,
and in fact should be faster since we added gzip and deflate support
to their stack. Our tests indicate that we load pages as fast as IE
as well. However we are rendering much more of the page and that
could be consuming considerably more CPU, making it appear to load
more slowly. I just tested the desktop version of facebook on my
phone and it works fine with our latest tree but I believe there is
an issue at login time that causes the IE SSL stack to use enormous
amounts of memory. We have someone working on this to try to find a
workaround."


Looks like this browser isn't as self-sufficient as I'd thought. It's dependent upon Mobile IE, something people already don't like. Slight improvements to it with gzip and deflate support aren't enough. Mobile IE in its current iteration needs to be segregated from the playing field.