Opera moves to WebKit and V8

Posted Feb 15, 2013 23:16 UTC (Fri) by josh (subscriber, #17465)
In reply to: Opera moves to WebKit and V8 by philipstorry
Parent article: Opera moves to WebKit and V8

> Except this is an engine that can be fixed by anyone when it's broken.

When "broken", sure; however, that doesn't stop sites from saying "best viewed in a WebKit-based browser". Already a fair number of sites only work on Chrome or other WebKit-based browsers; most commonly, mobile sites that just break, and supposedly "HTML5" demo sites that use -webkit-* prefixed CSS and otherwise only work in WebKit-based browsers.

Opera moves to WebKit and V8

Posted Feb 15, 2013 23:58 UTC (Fri) by philipstorry (subscriber, #45926) [Link] (1 responses)

Oh, here you'll find no disagreement from me.

Idiot web designers will be idiot web designers. And they'll assume WebKit means Safari, or that it means a mobile device. And they'll code for prefixed CSS but do it incompletely and sloppily.

I can't really do anything but condemn that.

But on the other hand, if these idiots can't even handle Chrome also using WebKit, then why does it matter if Opera is using Presto or WebKit?

They were going to support Opera badly either way. Just like they were going to support Chrome badly, or non-mobile WebKit instances badly.

Idiot web designers will be idiot web designers. :-(

Opera moves to WebKit and V8

Posted Feb 16, 2013 0:12 UTC (Sat) by josh (subscriber, #17465) [Link]

It matters because they can get away with it more easily if WebKit has a larger market share. Similarly, the larger the market share of Linux and OS X, the less easily people can get away with exclusively targeting Windows.