Blink: A rendering engine for the Chromium project
blog.chromium.org
Blink: A rendering engine for the Chromium project
1–10 of 326 posts
Re: Blink: A rendering engine for the Chromium project
#2This blog post doesn't make an engineering based argument* so I'm left with the business ones. Which sucks.
* - Just vague "we need to innovate faster" boilerplate. Which is what business people say when there's not a solid engineering based reason.
EDIT:
At the bottom of the project page are some engineering reasons:
Each person can judge whether it's worth forking or not.
Re: Blink: A rendering engine for the Chromium project
#3Re: Blink: A rendering engine for the Chromium project
#4Re: Blink: A rendering engine for the Chromium project
#5Interesting timing, given the Samsung+Mozilla+Servo news today.
Re: Blink: A rendering engine for the Chromium project
#6Just a few weeks after Opera decided to switch to Webkit. Interesting.
Re: Blink: A rendering engine for the Chromium project
#7I can't help but think that forking WebKit is a business based decision since Apple controls WebKit. This blog post doesn't make an engineering based argument* so I'm left with the business ones. Which sucks. * - Just vague "we need to innovate faster" boilerplate. Which is what business people say when there's not a solid engineering based reason. EDIT: At the bottom of the project page are some engineering reasons:…
b) Although it is a little hand wavey, they do make an engineering argument: "However, Chromium uses a different multi-process architecture than other WebKit-based browsers, and supporting multiple architectures over the years has led to increasing complexity for both the WebKit and Chromium projects."
Re: Blink: A rendering engine for the Chromium project
#8Just a few weeks after Opera decided to switch to Webkit. Interesting.
Re: Blink: A rendering engine for the Chromium project
#9Re: Blink: A rendering engine for the Chromium project
#10Just a few weeks after Opera decided to switch to Webkit. Interesting.