Weekly GNU-like #MobileLinux Update (13/2025): Crossing Platforms, Breaking Barriers

https://linmob.net/weekly-update-13-2025/

#LinuxMobile #Phosh #SailfishOS #Ubuntu Touch #Megapixels #FuriLabsFLX1 #Librem5 #PinePhone #postmarketOS

@linmob your take regarding OpenGL ES 2.0 is weird, that's a standard from 2007, now 18 years old. It's definitely not anything from "relatively new hardware". Qualcomm Adreno and ARM Mali GPUs have supported OpenGL ES 3.0 since 2013, if anything "relatively new" doesn't support it, the hardware simply isn't "relatively new", it's just dead on arrival

@adrianyyy I guess I worded that poorly. I was thinking of the combination of hardware and graphics drivers, where often OpenGLES 2.0 is a first base line reached, and later on, more is accomplished. Like with Asahi: December 2022 2.0, Mid 2023 3.1. Sadly, not all efforts move along as quickly, think etnaviv. Add the fact that the PinePhone Pro (ES 3.1, Mali T860) has issues with the new renderer..

(I could also look up when the last SoC with a Mali 4xx GPU was announced, but sure, that's DOA).

@linmob "Device X has driver issues but the hardware is capable" (be it bugs or just no driver at all yet in the case of your Asahi example) IMO is not valid criticism of GTK's choice of target APIs. Most importantly, the devices have the capability to run the newer APIs, so it reinforces the case for choosing them; second of all some specific devices having bugs is an exception to the rule and those shouldn't be reason hold back the ecosystem from adopting decade-old standards

@linmob overall I think your criticism is rather unfounded and I think the more constructive version of the comment about the GTK situation would be expressing hope for e.g. the pinephone pro perhaps seeing bugfixes for GLES 3.1 due to ecosystem adoption of the standard? I still don't really get your original intent...