Surprisingly, still GTK 3 which means software rendering.
If they get it to GTK 4 and recent WebKit release they'll get a lot of DMA-BUF usage to bring many of those WebKit->GTK->Compositor copies to 1 (or in some offloading cases, zero).
Luakit has been my main browser for a few years now. I like it, but it's slow and some sites don't work in it, so I fallback to ungoogled-chromium and LibreWolf quite often.
Oh, and sometimes there are WebKit incompatibilities[1], which means I have to hold back upgrading WebKitGTK on my system until it's fixed.
As a Lua user and a big fan of Qute et al browsers, I really want to like Luakit, but they've had a video bug[1] (they don't work at all) for a long time, and basically just ignore the issue as "not our bug" because it's apparently a webkit bug.
Well it is a Webkit bug. Epiphany/Gnome Web has the same issue. All they could do is either fix whats been broken in the Gtk port of Webkit for years or to start from scratch and use Chromium instead. Neither option is one that a small developer can easily do.
as in, read and reply to tedious posts, forward funny stories to my friends and just generally free us from our phones? the same way a video recorder watches tedious tv in our place and an electric monk believes in silly things for us?
It's extremely easy with GTK these days too because libpeas has a luajit backend (along with SpiderMonkey, Python, and of course anything native) and they all are backed by GObject Introspection to call into the C libraries/app.
Webkit is useless. if the project is not keeping updated , it will results in incompatible web engine . The webkit itself have so many incompatibility against latest web standards.
If they get it to GTK 4 and recent WebKit release they'll get a lot of DMA-BUF usage to bring many of those WebKit->GTK->Compositor copies to 1 (or in some offloading cases, zero).
reply