This morning’s announcement that Opera intends to abandon its Presto rendering engine has left designers and developers with a number of questions. I sent a few over to Opera’s Bruce Lawson to shed a little light on the situation.
So. “Any exciting news in the world of Opera today,” he asked knowingly.
Opera for desktops, Opera Mobile, and Opera Mini are all moving over to [Chromium] WebKit? Does this mean that
-o prefixing is dead-and-buried?
Eventually, yes—I don’t have timescales yet; obviously it’s not a trivial piece of work so there’s lots of testing involved. This change hasn’t happened yet, and Presto-based browsers will remain in the market for a while yet, so our advice is as it’s always been: code to standards and not to browsers, use all vendor prefixes (including the tiny few that we didn’t remove from Presto, and test thoroughly across browsers and devices.
The developer community seems pretty divided on this. Some say we’re moving towards an IE6-style “monoculture,” and some seem to think there’s enough diversity in WebKit implementations themselves that it’s a non-issue. What do you think?
I was initially worried, but it seems to me that WebKit has excellent diversity. And, of course, there is no monolithic WebKit. PPK counted 19 (I believe) on mobile alone. Of course, I have no crystal ball, but the fact that there are disparate, competitive players in WebKit suggests that it’s unlikely to stagnate the way IE6 did.
What impact will this have on web standards? Will this mean Opera has some say in Chromium’s roadmap, or are they more or less beholden to Apple/Google’s decisions now?
We have independence to add (or remove) anything we like from WebKit or Chromium via our fork, but we aim to promote interoperability, not harm it. We have eighteen years of experience making browsers, and have participated in making many standards that are integral to the modern web (Media Queries, HTML5, native video, etc.) so we have lots of ideas to contribute.
Can we expect radical changes to Opera products within the next version or two, or will it be a more gradual process? I can’t imagine a brand new rendering engine will just drop in clean.
A new version for Android is being demoed at Mobile World Congress in Barcelona at the end of the month (come and say hello—I’m the guy with the pink mohawk, stuffed into a cheap suit and uncomfortable shoes). After that I can’t really speak to timescales as I simply don’t know yet.
Will this free up Opera devs to work on new features, now that their primary concern isn’t just maintaining platform parity?
Yes—that’s the reason for doing it. We have a great reputation for inventing things that have been widely copied and have improved the consumer experience of browsing for all—things like Speed Dial, data compression, tabbed browsing, and mouse gestures, and we want to focus on those.
What improvements can we expect with the move to WebKit—accessibility, for example?
I can’t comment on individual features of future products. But you can be sure that I’ll be fighting to get accessibility improvements in there, just as I’ve fought to get them added to specifications.
10 Reader Comments
Wow!! that’s a big change for front-end devs… An interesting move for keep innovating, I hope so…
Gotta love Bruce. I miss working with that guy at Opera. I think this is a good movie. Opera has always been a bit of “fringe” desktop browser and this will help bring it more into the mainstream I think, at least in the US.
So does this mean we will eventually see an Opera Mobile build on iOS?
Definitely good news. I hardly ever code specifically for Opera but I’m more excited about what they come up with in the future. Webkit is awesome and pairing that with an innovative team like Opera is just gold for front-enders.
> Some say we’re moving towards an IE6-style “monoculture,” and some seem to think there’s enough diversity in WebKit implementations themselves that it’s a non-issue.
I actually _want_ a monoculture like this. Why?
Well what did diversity give us? A clout of vendor-specific prefixes and kludges like JQuery and LESS necessary to fix the mess of development.
What did the IE6 monoculture give us? An advance so important it necessitated “increasing the web’s version number”: AJAX.
This is a just and understandable move for opera.
But it scares me to think how much we’re moving towards a webkit monoculture.
“What did the IE6 monoculture give us? An advance so important it necessitated “increasing the web’s version number”: AJAX.”
And the world’s worst browser, which took a decade to die off.
The end of DragonFly? Noooo.
It’s pretty ironic how folks will complain about the diversity of implementations out there when trying to develop something interoperable, but then moan a little when things actually come into spectacular alignment around some clearly superior technologies like V8. A “monoculture”? We’re note even remotely near. Let’s celebrate this! If the Opera braintrust wants to contribute to webkit instead of Presto, that is a huge win for open source. And let’s not forget SVG: Opera’s implementation is hands-down the best out there. Personally, I’m hoping the SVG gods at Opera can address the longstanding multitude of SVG layout tests failing in webkit. These fixes are long, long overdue. Bruce? 🙂
Just a minor code nitpick; the font in the questions renders awfully in my browser. The css specifies p.question to use “Franklin ITC Pro Bold”, but then there’s also a tag within each question. The result is some franken-boldness that looks awful in my FF (OS X).
Got something to say?
We have turned off comments, but you can see what folks had to say before we did so.
More from ALA
Personalization Pyramid: A Framework for Designing with User Data
Mobile-First CSS: Is It Time for a Rethink?
Designers, (Re)define Success First
Breaking Out of the Box
How to Sell UX Research with Two Simple Questions