Linked by Thom Holwerda on Sat 19th Jan 2013 14:22 UTC
Opera Software This is actually pretty big news - both exciting and tragic at the same time. Opera has revealed Opera Ice, its next mobile browser, to PocketLint. This new browser represent a big shift in both user interface as well as rendering engine, since it has a new, unique interface, as well as a new rendering engine... New to Opera, that is, as it's a WebKit-browser.
Permalink for comment 550016
To read all comments associated with this story, please click here.
RE[12]: ...
by Laurence on Wed 23rd Jan 2013 09:53 UTC in reply to "RE[11]: ..."
Member since:

Except isn't really true of the newer browsers they have produced.

Yes and no. The important bits are sorted but there's still some "gloss" missing (text shaddows, etc). None of that is important though.

Sorry understanding caching and how it can help you is vital.

I know how cache works (did you miss my post where I've said I actually built my own browser - rendering engine and all. I know the HTTP protocol intimately).

For the record, most of my traffic isn't returning traffic and I often get huge spikes in traffic - so I want initial loads to be as minimal as possible.

Also I plan on serving most of the site under SSL if/when it does take off, so returning traffic will still need to recache all the content each new session.

So quit being a presumptuous ass just because someone doesn't buy into your BS Microsoft fanboyism.

I find it hard to understand that you call yourself an expert and are unwilling to work around limitations. I personally think it is sloppy considering there are plenty of decent techniques that preserve as much performance as possible while still catering to those users.

Once again, you're just cherry picking arguments thus missing the point as a whole. My project works perfectly under Lynx - you don't get a much bigger limitation than that.

I also said bandwidth is my number 1 priority - and that's also a much bigger limitation than having to decide who's framework to pilfer just to get rounded corners working on an older version of a crap browser.

You really need to stop with these dumb assumptions you keep making about me.

I suppose it depends on your budget and you willingness.

It's quite a niche product and most of the visitors are not running IE, so my willingness is pretty low.

As long as the site renders perfectly in webkit, gecko and presto - and the mobile.css renders perfectly all the mobile rendering counterparts, then I have more than 90% of my market covered. IE is lumped with Lynx; they will be supported because the site degrades gracefully. So checking in IE is really more an afterthought.

But as I said above, the only CSS stuff I'm using that the latest versions of IE miss is pretty irrelevant anyway. So I'm not about to add a few Kb to my initial footprint just fully to support features that really have no baring on the content on the site. (though sadly these days it seem some people are more interested in design than content. In my opinion content comes first and foremost)

I would give you a link to the test site just to clear this whole stupid discussion up - once and for all - if I believed you actually cared about the topic more than you cared about arguing with me.

Edited 2013-01-23 09:56 UTC

Reply Parent Score: 2