Bullshit-free Google Chrome Blink developer FAQ translation

1 Why is Chrome spawning a new browser engine?

The WebKit maintainers wouldn’t let us attack Apple directly, by changing WebKit in ways that would make it perform badly on OS X and iOS.

Because they share a rendering engine, developer effort to ensure Chrome compatibility currently benefits Apple platforms for free. To prevent this, we must make Chrome and WebKit behave differently.


  • soybeanstasher

    This is pretty dumb, even if intended for humor. The reasons laid out here are too reasonable for this silly attack. http://infrequently.org/2013/04/probably-wrong/

    • See, I read that article yesterday. And I think it strengthens this “bullshit-free” translation. That’s exactly what they’re saying, only they’re pitching the tone differently.

  • It is funny and probably contains a lot of truth but the value is lost in the hate. Anyway, what about Apple and their exclusive use of Nitro?

    • Nitro is the JS engine just like Google uses V8.

      • Ah ok maybe I misunderstood it. All the reviews I read basically made out that 3rd party browsers are slower due to not being able to use Nitro.

  • Will Tolley

    I’m sorry but I have to say this is probably the most ill-informed piece I have ever seen.

    I knew yesterday The Loop would have a negative slant on this as lately it’s become less balanced and almost a sort of mirror image of a site run by someone like Dan Lyons. With Google in Apple’s place.

    Google uses Macs. That is by and large their system of choice. The amount of times this has been established, whether by all Googlers visibly using MacBooks at I/O or in meetings or whatever is through the roof. The phenomenally huge community of Chrome and Google WebKit developers also seem to use Macs by and large. The idea that they don’t want to contribute to something that Apple uses, after half a decade of contributing more to WebKit than Apple themselves.. speaks for itself. I’m probably more of an Apple fan than one of Google, but they’ve contributed more to WebKit and along with it iOS and OS X than seemingly Apple fanboys (like the writer of that piece) would ever care to know. Hundreds of thousands of updates and unreal amounts of security fixes, along with paying out huge amounts of money for bug bounties.

    I know I sound like I’m ranting on, but I just don’t understand why people need to treat companies like religion. Just because Google is a so-called competitor to Apple it doesn’t mean they’re at war and sides need to be chosen. In fact up until this fork, which seems unambiguously like the right move and very necessary from a programming point of view, they’ve had a full-scale collaboration for years. Lines like “changing WebKit in ways that would make it perform badly on OS X and iOS” are just clearly written by someone almost deluded.

    There are some such good pieces being written on this that could have been tipped off like Steven J. Vaughan-Nichols’ piece at ZDNet (http://www.zdnet.com/blink-google-forks-webkit-7000013484/) or longtime WebKit contributor Peter Beverloo’s take (http://peter.sh/2013/04/welcoming-blink-chromiums-new-open-source-rendering-engine/). It’s a shame if a purely biased backhanded joke is the only thing that gets promoted.

    • Tone

      Bit of a rant but true.

    • Here is the new Web Browser Landscape..

      Render Engine – Browser – Company – Platform * Webkit – Safari – Apple – OS X & iOS * Blink – Chrome – Google (Android & ChromeOS) * Trident – IE – Microsoft – Windows * Servo – TBD (Firefox) – Mozilla (Firefox OS) / Samsung (Android & Tizen)

      Notice Anything? Each mobile platform provider is owning it’s own web browser render engine.

      Also, the reason why some people are mad about this move is because Webkit was winning the render engine battle because of Chrome’s adoption of Webkit. Opera just abandoned its render engine and joined Webkit. The more that browser makers agree to leverage the same render engine the easier and quicker it is to execute front-end web development.

      Browser should compete on feature sets not on how they interpret the paragraph tag or always add 10 pixel top-padding to the body tag. Could you imagine if TV makers had their own proprietary way of interpreting the video signal?

      You want to know why Flash became so popular? A major reason is because it was a single interpreter. If something was built in flash you didn’t have to check how IE 6, IE 7, Firefox, Safari, Chrome, and Opera chose to interpret your the code. You check how Flash Player interpreted your code and you were good to go.

      The vendors involved in the platform wars are using the Web Browser as a weapon and it is a pain for people that just want to make some cool stuff.

      • I think you also need to look at the history. The WebKit team’s process is so bloated to support companies doing ports like Samsung (historically) and Google. To turn around and say that the constraints introduced to help them make it too difficult to work show a pretty amazing lack of awareness.

        That said: Great. Hopefully, this’ll let WebKit streamline their processes a bit. And maybe Blink will turn out so well that Apple will fork it in turn.

  • Google is the master of saying one thing and doing the total opposite.

  • Mother Hydra

    I love me some vitriol as much as the next hydra but this doesn’t approach the quality-level needed to pull off this humor. Dear Rob Isaac, leave this stuff to the professionals like the Onion and Macalope.

  • I don’t know about anyone else, but I, for one, am looking forward to The Browser Wars 2: Attack of the Forks.

    “Use the Fork, Luke!!”