3 ms·

Thanks for your comment : that makes more sense now. I had the assumption that efficient SVG rendering in Safari was critical and a UX bottleneck to work on fr

Thanks for your comment : that makes more sense now. I had the assumption that efficient SVG rendering in Safari was critical and a UX bottleneck to work on from an Apple perspective, but maybe Apple hardware makes it moot.

nzimmermann86 5y ago
It's not the hardware per se. CoreGraphics on macOS/iOS utilizes the GPU for painting, which is much faster than software rendering. Cairo, used for the Linux GTK/WPE ports, is software based, and thus much slower, when painting large scenes. Therefore for embedded devices using WebKit/Linux GTK/WPE ports we see a huge improvment with the layer based engine. Also macOS/iOS benefits though -- animations are even faster, and you don't easily run into problems, when animating parts of a complex document. It's shown in the video linked in the article at the end: > 20% frame rendering time improvement on an already quite efficient rendering pipeline (Safari / macOS using CoreGraphics on M1 machine).
- Pulcinella 5y ago
  I believe CoreGraphics is CPU based. CoreAnimation utilizes the GPU.
- The_rationalist 5y ago
  Why don't you use an embedded chromium instead? Skia bring SOTA gpu performance and the SVG backend must be mature.Even if there were a need for improvement or for a new SVG backend, contributing it to chromium instead would be a much more altruistic gift for mankind, since the improvements would affect billions of end users, instead of the webkit idiosyncrasie.