Slashdot Mirror


Opera Confirms It Will Follow Google and Ditch WebKit For Blink

An anonymous reader writes "Google on Wednesday made a huge announcement to fork WebKit and build a new rendering engine called Blink. Opera, which only recently decided to replace its own Presto rendering engine for WebKit, has confirmed with TNW that it will be following suit. 'When we announced the move away from Presto, we announced that we are going with the Chromium package, and the forking and name change have little practical influence on the Opera browsers. So yes, your understanding is correct,' an Opera spokesperson told TNW. This will affect both desktop and mobile versions of Opera the spokesperson further confirmed."

6 of 135 comments (clear)

  1. The Angels have the Google by Snowhare · · Score: 5, Funny

    Remember: Don't Blink

  2. Re:User configurable by larry+bagina · · Score: 5, Insightful

    Google says they're forking for technical reasons -- Google uses a different thread model and security model than Apple and making a hard break makes for easier maintenance. If they're going to keep both rendering engines around and updated then there would be no reason to fork in the first place.

    --
    Do you even lift?

    These aren't the 'roids you're looking for.

  3. Re:So webkit != Blink! by Billly+Gates · · Score: 5, Insightful

    I hope they don't keep -webkit-* enabled forever. The CSSWG agreement doesn't say anything about phasing out existing prefixed properties, but keeping them around with outdated syntax/behavior doesn't seem like a good idea. It was never good practice to use a prefixed property without its unprefixed version. So if removing prefixed properties breaks some pages, that means they were broken in the first place.

    You must be new here :-)

    Things stay freaking forever in the industry once it someone or a corporation is dependent on something. IE 6 and XP is still being used with its users considering an open standard broken because it breaks and broken standard to them which is open. Logic is backwards but CMS never get replaced, sites stay, and users whine and blame YOU if something doesn't work. Never the product.

    This is a classic lesson on why standards are so important and why going proprietary is bad. Not a closed vs open debate more than a standard one. Stuff never goes away even if it is broken.

  4. Re:Differentiation? by SpectreBlofeld · · Score: 5, Informative

    They're obviously hurting financially. By switching to Webkit (and now Blink) they were able to lay off over 90 developers, some of whom had been with the company for 15 years. This sucks - for the developers, obviously, but I'm sure nobody was happy about making that call; but according to salarylist.com, the average software developer salary is around $81,000/yr which times 90 developers is 7.29 MILLION dollars a year. Not sure if Norway dev pay is equivalent to the US average, but you get the rough picture. That sort of sum could make or break Opera as a company.

    I've been a fan of Opera browser for a very long time - I started using it right after it became free. Opera pioneered a great deal of features that are browsing must-haves today, implementing them years before any competitor. They remind me of another company that hailed from their land-mass-sharing-neighbors in Sweden: Saab. A car company that pioneered many innovations that were later incorporated in automobiles across the board. The first to do this, the first to do that - turbochargers on production cars, cabin air filters, very high crash safety standards, active seat belts (okay, that one didn't last long), active head rest restraints, refrigerated glove box (for taking that Chardonnay to the picnic of course), headlight washers, heated seats, the use of computers to automatically monitor and adjust the engine's operations based on the type of fuel used and sensor input, direct ignition, traction control, air conditioned seats, etc, etc, etc. Now compare to this list of Opera 'firsts':

    http://operawiki.info/OperaInnovations

    Saab was bought by GM. When that happened, all their cars were mandated to be cross-platform cars. They shared chassis with other cars; some models (and SUV and a hatchback) were blatant rebadges of a GM SUV and a Subaru (nicknamed the Saaburu). Now Saab is no more.

    Sounds like what is happening to Opera, unfortunately.

    I know 'car metaphors' are a Slashdot tradition, but I find this one particularly apt.

  5. Re:Poor Opera by Archenoth · · Score: 5, Insightful

    I use Opera.

    I don't use it for it's rendering engine, but rather for all of the functionality it has by default that other browsers simply cannot do. (Even with extensions.) So, the fact that it is becoming more compatible with most websites is great news for me. It means they can continue to innovate like they have done for years. (Most modern browsers use things that were created by Opera ages ago.)

    They are not becoming Google's bitch because rendering was never their main feature, they are simply adopting the engine that everyone develops for while retaining the functionality that Opera users actually use. Sure, some of us will decry the switch because Presto was one helluva light engine and we lose the work done on it, but other then that, this is actually good news.

    --
    The arch foe.
  6. Re:So webkit != Blink! by drinkypoo · · Score: 5, Insightful

    Standards keep the various vendor's implementations compliant.

    Laws prevent crimes.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"