Just that ‘use skia’ isn’t a particularly good answer either.
I’m somewhat dismayed that Linux doesn’t seem to have a solid 2d graphics library.
Say you want to write a GUI app.
On Windows, you've got Win32. It's old, but it'll still work and look new.
MacOS you have Cocoa.
Linux, you have Xlib. Wait, that doesn't provide enough. We have to use a toolkit, like Gtk or Qt. Which one if we want to look integrated? How do we integrate 3D APIs?
Then there's Wayland. You want to use that instead because X is deprecated. But there's no extensive API--it's basically only a way of putting rectangles on the screen. You have nothing to get you started unless you stick hard to Gtk, Qt, or do really rudimentary graphics, and cross-compatibility is really ugly.
A few years ago there was talk of the Cairo API (not necessarily the Cairo library implementation of that API) being adopted as part of a C language standard.
That seems not to have happened. Consequently, if you program in C or in a language that depends on C libraries to get stuff done, there's still no go-to library/API for 2D drawing.
Also, the scope of "2d graphics" is not fixed either. Does it include a scene graph or not?
Skia works well but has an unstable api, hard to interested build, and limited language bindings, is poorly documented and is controlled/developed by Google.
QT has a giant set of dependencies and no independent graphics library.
It wasn't a very common UI scene, so it wouldn't be expected that other libraries had optimizations for that type of content (specifically with the "everything is slightly rotated" part)
It was also a scene that curiously didn't involve any paths or shapes other than rectangles, which is where GPU-accelerated canvas' all really run into trouble.
Also note that the presentation was from 2016, and many of these libraries (such as Skia) see heavy ongoing work so that data is all quite outdated and unreliable at this point.