Google seems on a "replace open with less open" streak, with google reader and caldav shuttering, and now this. The caldav situation especially i cannot conceive as anything but a business decision given that they're keeping it around for those people they like.
Blink: A rendering engine for the Chromium project
31–40 of 326 posts
Re: Blink: A rendering engine for the Chromium project
#32Does this mean that Chrome for iOS will be revoked out of the AppStore?
Nope, no changes for Chrome for iOS: current version already uses UIWebView and will continue to do so. The rest of the infrastructure (networking, etc), is Chrome code.
Re: Blink: A rendering engine for the Chromium project
#33Does 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.
So Google will be using 2 increasingly different rendering engines for Chrome in the future? Well that sucks. Apple really needs to allow other rendering engines on iOS, or at least be forced into it. People complain about the "webkit mono-culture", but a huge platform like iOS actually mandating you use webkit, and their single version of webkit, is a lot worse.
Re: Blink: A rendering engine for the Chromium project
#34I 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:…
If there is an engineering argument, I'm guessing it's to do with multi-threaded DOM+JS, given the mention of multi-process architecture.
Also, how much does Apple really control WebKit? At a glance, it looks to me like FOSS. (Apple might be the maintainer, but it seems trivial to fork it in a different direction.) Perhaps this is a more nebulous "thought leadership" kind of thing?
Re: Blink: A rendering engine for the Chromium project
#35is this a fork of webkit2 with the split process model built in?
I think it's the other way around: they want to eject the newer Webkit 2 from their fork rather than do the work to adopt it.
Re: Blink: A rendering engine for the Chromium project
#36Google seems on a "replace open with less open" streak, with google reader and caldav shuttering, and now this. The caldav situation especially i cannot conceive as anything but a business decision given that they're keeping it around for those people they like.
With regard to open, Chromium is a nicely open source project, and we're really quite committed to transparency in the project. See http://www.chromium.org/blink#new-features for some of our policies in this direction.
Re: Blink: A rendering engine for the Chromium project
#37Re: Blink: A rendering engine for the Chromium project
#38is this a fork of webkit2 with the split process model built in?
I think it's the other way around: they want to eject the newer Webkit 2 from their fork rather than do the work to adopt it.
WebKit2 is a similar, but different, multi-process model. Chromium never compiled it in, but the integration imposed various constraints both on Chromium and on WebCore. That's certainly one of the reasons we've introduced Blink.
Re: Blink: A rendering engine for the Chromium project
#39Does this mean that Chrome for iOS will be revoked out of the AppStore?
Chrome for iOS is just a wrapper around Safari.
Chrome for iOS uses a UIWebView for rendering (effectively Safari), but uses the Chromium networking layer, UI (omnibox), etc. Arguably though rendering/JS is a big part of what makes the browser the browser, but it isn't everything.
Re: Blink: A rendering engine for the Chromium project
#40Super excited about this! There was a long discussion on the webkit mailing list after google tried to add support for multiple language VMs in webkit. The goal was to have a native Dart VM.
https://lists.webkit.org/pipermail/webkit-dev/2011-December/...
If I remember correctly, the patch was not merged in. I guess now google can do whatever it wants!