Announcement

Collapse
No announcement yet.

WebKit Looks To Drop Google Code, V8, Skia

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by Marc Driftmeyer View Post
    Oliver Hunt right answers this connumdrum here:

    https://lists.webkit.org/pipermail/w...il/024408.html
    He says nothing about Qt

    Originally posted by Marc Driftmeyer View Post
    GTK+ chimed in to clarify it doesn't support V8.

    https://lists.webkit.org/pipermail/w...il/024410.html
    GTK+ is obsolete and not relevant anymore.

    Comment


    • #17
      Originally posted by ворот93 View Post
      He says nothing about Qt
      No 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


      • #18
        Originally posted by GreatEmerald View Post
        If 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?
        Relax. They are referring to platform adaptations. Have a look at https://trac.webkit.org/browser/trun...bCore/platform
        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


        • #19
          Originally posted by phoronix View Post
          Following 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...
          Reading through the mailing list, the suggestion to remove Chromium support came directly from Google and they'll even write the patches themselves:
          https://lists.webkit.org/pipermail/w...il/024384.html

          Comment


          • #20
            Originally posted by Ericg View Post
            No 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.
            I could be wrong but I think that QtWebKit is using standard JavaScriptCore and V8 is only being used for QML execution.

            Comment


            • #21
              Originally posted by ворот93 View Post
              He says nothing about Qt
              Qt will be fine.

              Originally posted by Benjamin Poulain
              QML uses V8. That does not matter for WebKit.
              QtWebKit uses exclusively JSC.

              Comment


              • #22
                Originally posted by Marc Driftmeyer View Post
                Full scale adoption of LLVM/Clang/LLDB/Compiler-RT/libc++abi/libc++ will be adopted in WebKit. You can bank on it.
                Google is a huge contributor to these projects and is pushing them just as hard as Apple (to the point that I've seen some of Google's engineers claim Clang as "their" compiler even though the initial code drop and continued release management is by Apple-employed engineers). Google has been doing a lot specifically with its WebKit (now Blink) code and the Clang family of projects. Most Google developers I've worked with use OS X as their primary dev machines with Windows/Linux VMs and secondary boxes just for building and testings the ports. So everything you say is true but essentially irrelevant. Blink is less likely to ever _only_ work with Clang, but strong integration with and support for Clang and related tools will remain a top priority for Blink. I expect to see more use of Clang tools and analysis in Blink as time goes on since Google's dev tools team is writing most of those tools, often explicitly at the behest of Google's Chromium team.

                Comment


                • #23
                  Originally posted by ворот93 View Post
                  He says nothing about Qt


                  GTK+ is obsolete and not relevant anymore.
                  GTK is not obsolete...Its still an actively developed toolkit that is used by many.
                  Last edited by bwat47; 04-07-2013, 11:10 AM.

                  Comment


                  • #24
                    Originally posted by bwat47 View Post
                    GTK is not obsolete...Its still an actively developed toolkit that is used by many.
                    Yeah but GTK is in an awkward position nonetheless with Clutter taking over more and more of its duties even within Gnome.

                    Comment

                    Working...
                    X