Bruce Lawson on Opera’s Move to WebKit

by Mat Marquis

10 Reader Comments

Back to the Post
  1. Wow!! that’s a big change for front-end devs… An interesting move for keep innovating, I hope so…

    Copy & paste the code below to embed this comment.
  2. 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.

    Copy & paste the code below to embed this comment.
  3. So does this mean we will eventually see an Opera Mobile build on iOS?

    Copy & paste the code below to embed this comment.
  4. 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.

    Copy & paste the code below to embed this comment.
  5. > 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.

    Copy & paste the code below to embed this comment.
  6. This is a just and understandable move for opera.
    But it scares me to think how much we’re moving towards a webkit monoculture.

    Copy & paste the code below to embed this comment.
  7. “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.

    Copy & paste the code below to embed this comment.
  8. The end of DragonFly? Noooo.

    Copy & paste the code below to embed this comment.
  9. 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? :)

    Copy & paste the code below to embed this comment.
  10. 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 <b> tag within each question. The result is some franken-boldness that looks awful in my FF (OS X).

    Copy & paste the code below to embed this comment.