From http://skia.org : “While engineering of the core components is done by the Skia development team, we consider contributions from any source.” Implying I can’t lead engineering of “core components” of the vector graphics renderer unless I work at Google.https://twitter.com/auchenberg/status/1088587621721231361 …
-
-
BTW, there’s a related thing you all are going to have to deal with whereby upstream Skia has removed all SIMD code on MSVC.
-
Also, Google will never take WebRender/Pathfinder into Chromium. They’ll just reimplement pieces from it in Skia, as (I discovered recently) they have already done with some of Pathfinder’s AA stuff. Skia is public API on Android; they can’t migrate away from it.
- 1 more reply
New conversation -
-
-
Ignoring Skia, just chromium is a huge cost to fork and maintain without a staff of the size MS is assembling. Brave rebases to track chromium stable as fast as or faster than than other chromium browsers, but we do it by keeping our changes on the outside as much as possible.
-
If anyone has the staff to do this, it is Mozilla. But not for long.
- 3 more replies
New conversation -
-
-
I don’t think you want to fork Skia for the sake of it. There has to be three conditions a: good enough reason to do so, upstream maintainer unwilling to find a solution/middle ground, how key it is to your goals/objectives.
-
Now the question is whether Mozilla’s top goal is “promote an open web” or “build secure software using rust” (just an example). The economics might not support both.
- 1 more reply
New conversation -
-
-
it's going to be fascinating to see how much if any of a fork the Edge team maintains from pure Chromium for anything Microsoft finds strategic that doesn't get accepted into Chromium. eg Brave doesn't take all patches so has a fork of sorts
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.