@mntmn It's been there for a few releases already, though it was getting additional improvements over time. It's been snappy on the L5 in the last months. 2.52 has been released today, it's not yet in Debian (though 2.51.93 is in experimental), but should be soon and it looks promising too: https://webkitgtk.org/2026/03/18/webkitgtk-2.52-highlights.html
(it's maintained by the same people as WPE)
@mntmn Recent versions of WebKitGTK with the new dmabuf renderer (which it shares with WPE AFAIUI) perform similarly well. It only needs some papercuts around touch input handling solved - I have recently worked on some, but there's a few more left.
@marmarta @dos @camerontw Honestly the right answer to the question of who to disappoint is always going to be "the developers and designers of the thing." Our egos lead us to solve product problems over user problems, to end up with supporting a bunch of "use cases" no real user has.
@marmarta What I meant by "aesthetics" would also contain (or perhaps actually be defined by) this desire to streamline, so thanks for putting it into much clearer words than I could 😀
@marmarta Good UX requires validation by testing with actual users achieving their goals, not designers making things appeal to their aesthetic sensibilities (which seems to drive at least some of these anti-power user sentiments). The latter can be helpful too, but since most designers working on FLOSS lack resources needed to do the former it often ends up actually detrimental to UX...
So, some great conversations at #fossback26 design. And some that really frustrated me. During the "how to bridge the gap between "ultra-nerdy" devs and designers" barcamp, someone said "we have to decide who to disappoint when making design decision", and someone else said "spoiler: it's the power users".
If our attitude towards #uxdesign is "fuck the power users", we'll never have good UX in open source.
It's funny how this phone keeps feeling faster as it gets older.
Looks like GTK is starting to get its renderer inefficiencies sorted out, as updating Flatpak runtimes has made Tuba smoother than ever 😄 #librem5
@Gina @simonjust I'd probably have a hard time if I were to switch to Android after all this time, so it's all relative 😉
Services and governments requiring use of Android/iOS applications is a very recent phenomenon and I don't think it's too late to resist that yet.
@simonjust @Gina There are devices out there that are functional without relying on Android. I've been using them as my main phones for the last ~18 years (first Neo Freerunner, then Nokia N900, now Librem 5). Other people are currently using PinePhones, OnePlus 6/6T, Pocophone F1, Pixel 3a and a few others.
Truth be told, for quite a while even with laptops you had to put some effort before going shopping to ensure you'll have a good experience with GNU/Linux.
@simonjust @Gina Not really? It just tucks it under the carpet to be dealt with by Android.
@simonjust @Gina Now make it drop the Halium layer and liberation will be complete:)
@simonjust @Gina You can't do that with *any* mobile OS, open or not, and you absolutely certainly still won't for a good while. It's not a good goal to target.
You can already use it on specific well-supported devices, or work on supporting other specific devices well. That's how you can make a tangible difference today.
@johanpeitz I wanted to know whether a regular love2d compiled on whatever platform will be able to run it, so I take that as a "yes" 😁
@johanpeitz I see it's using LÖVE - does it work with the regular upstream interpreter?
@emill1984 Wszyscy wokół trąbili, ale dwadzieścia lat temu 😜
@Luigi311 This seems about the same as on Librem 5 then with its 4-5 hours of active use. It's idle time that's more challenging there.
Hi, I'm dos. Silly FLOSS games, open smartphones, terrible music and more. 50% of @holypangolin; 100% of dosowisko.net. he/him/any. I don't receive DMs.