Does this mean that Chrome for iOS will be revoked out of the AppStore?
Blink: A rendering engine for the Chromium project
11–20 of 326 posts
Re: Blink: A rendering engine for the Chromium project
#12I 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:…
http://www.chromium.org/blink/developer-faq has a bit more information, as does http://www.chromium.org/blink#architectural-changes. There really are good architectural reasons to go in this direction.
Re: Blink: A rendering engine for the Chromium project
#13I 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:…
Apple doesn't actually control WebKit. A decent proportion of reviewers at http://trac.webkit.org/wiki/WebKit%20Team are Google employees.
The engineering argument is that the differences between Chromium's multi-process model and WebKit2 are big enough that, in order for both projects to move forward, Google needs to fork WebKit. I'm not competent to judge whether this is actually true.
Re: Blink: A rendering engine for the Chromium project
#14Interesting timing, given the Samsung+Mozilla+Servo news today.
Servo's been around for a while: https://github.com/mozilla/servo/graphs/commit-activity
I know (been playing with it and rust for some time now), but it's not received half the attention it received today. I mean, the Verge covered it...
Re: Blink: A rendering engine for the Chromium project
#15I 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:…
[deleted]
Re: Blink: A rendering engine for the Chromium project
#16So when can we expect Chrome to use Blink?
Re: Blink: A rendering engine for the Chromium project
#17Does this mean that Chrome for iOS will be revoked out of the AppStore?
No, it just means that instead of Chrome for Android and Chrome for iOS having different versions of WebKit, Chrome for Android will use Blink and Chrome for iOS will use the system WebKit, as it does now.
Re: Blink: A rendering engine for the Chromium project
#18Standing ovation. This is most welcomed news since Opera's move to WebKit to keep the current browser innovation pace.
Coupled with Mozilla's announcement of its partnership with Samsung to move Servo forward this is great news for the future of the web. Hopefully multi-process/multi-threaded rendering engines will address some of our current performance gripes with the DOM and open the gate for even more complex UIs and interactions.
Re: Blink: A rendering engine for the Chromium project
#19Does this mean that Chrome for iOS will be revoked out of the AppStore?
Chrome for iOS is just a wrapper around Safari.
Re: Blink: A rendering engine for the Chromium project
#20I 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:…
Chromium uses a different multi-process architecture ... and supporting multiple architectures over the years has led to increasing complexity ... we anticipate that we’ll be able to remove 7 build systems and delete more than 7,000 files—comprising more than 4.5 million lines
How is that not engineering based?