Sebastian Krzyszkowiak @dos@librem.one

@exalm@floss.social @lorabe@floss.social They are so expensive because they're buggy, I'm about to push a fix for that. But yeah, live thumbnails will wait for gtk4 indeed :)

@lorabe@floss.social phosh itself doesn't render that much, so maybe aside of smoother scrolling in app list it won't really matter for performance - the apps getting ported matter much more. Using GTK4 with GL in phosh will enable us to make it more fancy though, so it's still desirable.

However, we need something like https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/2992 to get merged first before that can happen.

Fun fact - the biggest difference comes from this single commit: https://gitlab.gnome.org/GNOME/gtk/-/commit/57e354c297e1703079c2bc6fb51211b24d884ac3

Then the new "ngl" renderer and fixes in the Wayland backend boost the performance even further.

GTK4's GPU-accelerated GL renderer(s) got a major performance boost in the last few days! Previously it struggled to render simple UIs with single digit FPS on the Librem 5; now it can get pretty fancy :) #librem5 #gnome #gnomeonmobile #gtk

@karmanyaahm Compiling apps on it is what I do since I have received it, but so far I was doing the actual development on a PC, connecting to the phone via ssh. So now it goes a step higher :D (this isn't new though, AFAIK @agx was doing it first ;))

phosh running inside a container under phosh, plus phosh's source code in Qt Creator - all on the Librem 5. Perfect for when you want to work on the phone on the phone :D #librem5 #gnomeonmobile #phosh #docker #gnome #gnu #linux #mobile

@BrianA @kde@mastodon.technology @purism Runs well! Just a few hours before taking that photo I had postmarketOS with PlaMo running on that very same device (using only the internal screen though)

Here's Plasma Desktop on PureOS Byzantium running on the Librem 5 phone docked to an external display - just because :D @kde@mastodon.technology @purism #librem5 #kde #plasma #mobile #gnu #linux

@linmob I think that term may mean several things. There are commercial projects released on free licenses (wink wink); there are some licenses made with commercial interests in mind that pretend to be "open source" but in fact don't match the definition; and there are projects that sell their builds of fully FLOSS software as a way to finance the development (so you can build for free on your own, but people buy it for convenience and support).

@linmob In what context?

@white_gecko I need to finally dust off that old build tree on my disk and make SHR run on the Librem 5... :D

@gamey Ah, I'm using the Librem 5 and acceleration works fine there. It's not as snappy as Firefox is, but it's snappy enough for Hydrogen ;)

@linmob @lowkeylone I'm using Hydrogen as Epiphany's web app as my primary mobile Matrix client right now and it works pretty well.

"me in the morning, right after I turned the switches on"

This may not be the most impressive winter selfie (it's a 8M sensor outputting 0.3M after all), but you got to start somewhere :) #librem5

I did nothing but taking the photo (looped in a script with v4l2-ctl and dcraw; then displayed on screen using Eye of GNOME) - all the credit goes to Dorota and Martin, and the work continues there: https://source.puri.sm/Librem5/linux-next/-/issues/43

@Alexmitter @bleakgrey Thankfully it's not the underlying tech that makes it hard - it's just a matter of tooling and culture around it, so fortunately it does seem like it's just a matter of time and maturity.

@Alexmitter @bleakgrey Yeah, I find the fact that it's super hard even for the *user* to patch libraries used by Flatpak apps to be its huge problem. For you and me it's the scrolling bug, someone else may need a quick hack to improve accessibility, someone else may want to test their patch on real apps before contributing upstream... Flatpak makes this hard for no good reason. I hope this will get better with time as power user needs get recognized and proper documentation gets written.