229
Google Keeps Making Smartphones Worse
(jacobin.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Jul 2025
229 points (98.3% liked)
Open Source
39214 readers
229 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
Isn't that proprietary? So not really an alternative, even if it is so-called "Real Linux" for the Linux fanboys.
Some of the UI isn't open, otherwise it is Qt / Wayland / pyside with stsndard pkcon / rpm package manager and I program mine in Guile.
And the UI isn't the serious issue. The serious issue is propietary firmware which prevents you from really running Android / whatever on a vendor phone and also that a phone does not have one but around five different processors and only the "OS" one can be controlled by your own software. An Intel Pocket PC is far better in that regard, except that it won't work as a telephone.
How much is some? Can a usable, fully-free version be made without those non-free components? Given that the UI is the thing that mediates user interaction with the OS, I would suggest that a proprietary UI is in fact an issue.