Edge moving to Chromium and Chromium taking patches to build with MSVC while Skia upstream removes SIMD support when compiling with GCC and MSVC is an interesting situation.
-
-
-
Wow! If I were MS I’d just use fork Chromium to use D2D.
- 13 more replies
New conversation -
-
-
How do Skia and Cairo compare? I've only ever used Cairo personally and I found it easy enough for the most part. With good language bindings too.
-
Skia is way ahead in terms of performance and GPU support. Sad, because Cairo is much better of an open source citizen, IMO :(
- 2 more replies
New conversation -
-
-
Chrome would never use Cairo as it’s LGPL. I remember doing an audit of Chromium dependencies and they are all ZLIB/MIT/BSD. At one point there was an http://ffmpeg.so exception. One of the reasons is Google static links for better load time and runtime perf (no PLTs).
-
Interesting, hadn’t considered the licensing issues.
End of conversation
New conversation -
-
-
Cairo was awesome! Even for a noob like me
-
Cairo is excellent at all the little things—documentation, ease of use, contribution culture, portability, open process—that are unimportant for big companies but really important to be a good open source citizen.
- 4 more replies
New conversation -
-
-
Cairo suffers from all the things other great libs (like gstreamer) suffer from. A gnarly web of dependencies and strict adherence to Autotools and pkg-config. This is also a kind of unfriendliness. I'd never suggest adopting it.
-
Cairo build is not actually that bad. It is possible to build cairo standalone. It does use pkg-config but I usually just make a separate CMakeLists.txt. It is problematic distributing in an app for say Android or iOS. Signing and LGPL are not really compatible.
- 7 more replies
New conversation -
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.