Originally posted by GreatEmerald
View Post
Announcement
Collapse
No announcement yet.
WebKit Looks To Drop Google Code, V8, Skia
Collapse
X
-
Google never adopted WebKit 2 proposed and implemented by Apple Safari, GTK+, Qt, Win.
Full scale adoption of LLVM/Clang/LLDB/Compiler-RT/libc++abi/libc++ will be adopted in WebKit. You can bank on it. All this support is standard for OS X, FreeBSD, even Debian FreeBSD and Debian proper is including all of this to rebuild their entire archive to support both GCC/libstdc++ and LLVM/Clang/libc++.
If people want to maintain live copies of both Blink and WebKit they are always free to do so. I'm just thrilled not having to maintain GBs of crap from Google I never cared to check out with trunk.
It's also great news that GTK+ is adopting cmake so the gyp build crap is also going bye-bye.
Comment
-
Originally posted by CTown View PostThe Qt5 version of QtWebkit uses the V8 engine doesn't it? So, does QtWebkit now become QtBlink?
https://lists.webkit.org/pipermail/w...il/024408.html
GTK+ chimed in to clarify it doesn't support V8.
https://lists.webkit.org/pipermail/w...il/024410.html
Comment
-
Originally posted by GreatEmerald View PostBut if it's just optional, usable code, why would they want to drop it? Hide it behind a compiler flag if more compilation speed is desired, and that's all.
So no - with nobody interested in maintaining it, I'd give it a month before it's hopelessly broken by changes made to the more useful bits of the codebase - and I'm probably being optimistic at that. So why would you *not* delete it?
Comment
-
Originally posted by Marc Driftmeyer View PostOliver Hunt right answers this connumdrum here:
https://lists.webkit.org/pipermail/w...il/024408.html
Originally posted by Marc Driftmeyer View PostGTK+ chimed in to clarify it doesn't support V8.
https://lists.webkit.org/pipermail/w...il/024410.html
Comment
-
Originally posted by ворот93 View PostHe says nothing about QtAll opinions are my own not those of my employer if you know who they are.
Comment
-
Originally posted by GreatEmerald View PostIf there was code specific to Safari and Chrome in WebKit, how did it get there in the first place? I mean, if it's browser specific, why have it in mainline Webkit, instead of in the actual browser?
Chrome is written using a custom toolkit based on the Skia graphics library. I'd be very surprised if there is/was any user of the Chromium adaptions aside from Google. Removing unmaintained platforms is absolutely logical.
Btw: I can imagine that the android adaptions will stay if anyone if interested in providing a WebKit-based browser for Android.
Comment
-
Originally posted by phoronix View PostFollowing yesterday's announcement of Google forking the WebKit rendering engine to form "Blink" (also with the support of Opera), Apple developers working on WebKit are now looking to strip away Google/Chrome features from upstream WebKit...
Comment
-
Originally posted by Ericg View PostNo but what he did say was that they were dropping support for all JS engines except the one. If Qt / Digia want to still use V8 then, yes, they'll have to move to Blink. But if they're keeping it as QtWebKit then they'll stick with the default engine.
Comment
Comment