4 ms·
As a former embedded developer, I'm surprised nobody has come up with a basic purpose-built UI that skips all of the bloat (a phone doesn't need a WM), and just
by mindslight 5y ago
As a former embedded developer, I'm surprised nobody has come up with a basic purpose-built UI that skips all of the bloat (a phone doesn't need a WM), and just reliably performs basic functionality like voice calls and textual messages. Are the performance problems further down the stack (eg graphics driver), or are developers just too wed to the maladapted idea of running full web browsers on a phone, or what?
With the 4G partial shutdown I'd be in the market for a Pinephone but I just don't have time to do extra tinkering right now. I'll probably just limp along with my current pocket device and attempt to go VOIP-only.
- seba_dos1 5y agoEveryone keeps talking about "building a basic purpose-built UI" for many many years now, but that's pretty much a weekend project that could be easily built on top of already existing abstractions that somehow doesn't seem to gain dev traction. Zhone and Paroli already existed in the past, but most people gravitated towards more capable options. It's like people actually want their smartphones to be somewhat smart. Or maybe there are as many sets of things considered "basic" as there are people. Pick your explanation.
- pjmlp 5y agoEasy, the Linux phone is going to happen on the same day as the Linux Desktop finally arrives. Instead of collaborating on a single development and consumer experience, each of these efforts go out doing their own thing. Meanwhile companies like Nokia[0] and Google come and assert this is how it is going to be, not happy move on. The large consumer market, and App developers, don't care that many Linux syscalls aren't considered public APIs and communities like Termux refuse to acknowledge that. So every couple of years these attempts keep being rebooted, all the way back to OpenMoko. [0] - We all know why Nokia efforts bombed, and now their brand is also tied to Android phones
- eternityforest 5y agoI sure wouldn't pay money for something that can't run a browser. Such a device would probably not be any better than a $20 flip phone from eBay. They still make them.
- mindslight 5y agoCan you really not imagine any application without the bloat of a web browser, that wasn't on flip phones? Have you never gotten used to muscle memory to control a curses app? I used to develop interfaces for 5 MIPS PIC microcontrollers that were more responsive than 98% of today's consumer market. When I'm on the go, the last thing I want to be doing is waiting for UI lag from too many layers of frameworks running on a low power processor, never mind the poor battery life.
- eternityforest 5y agoThe modern web is very unlikely to go away. And we use the internet for everything these days. Why would I want the risk of being caught an hour from home, suddenly needing to do something that can only be done on a browser? They'd have to rely so much on individual apps for everything, but without layers of frameworks, the apps might not exist, because it would cost more to make them, and there might be fewer programmers in the world without those frameworks making it easy. Making non browser phones useful would require really big change to the whole mobile ecosystem, or else phones could no longer serve their present role as do-everything devices. I only know about 3 ncurses type TUI apps(No idea if they're actually ncurses under the hood). Nano, nmtui, and a demo test app I built for developing plugins. I don't use any of them unless I'm SSHed into things, because tech has reached the good enough point where even Electron apps are pretty snappy on an SSD.
- pjmlp 5y agoAs owner of a Sony CMD J5, I am pretty sure a browser has been there on such phones for quite some time, even if they could only see WAP pages.
- mindslight 5y agoSure, but you know that's completely orthogonal to what I'm saying. There is a big difference between a WAP browser and the webapp runtime we now call a browser. The latter replaces purpose-developed apps running primarily off local storage with ever-present client-server latency, best-effort presentation, and attention-required input for every single interaction. In fact I'd say the early WAP browser is closer to an example of the type of lean, discrete-button-press-controlled application I'm advocating than the touchscreen "browser" of today. And sure a full contemporary browser comes in handy in a pinch, but thinking it suffices for routine everyday tasks on a small form device is terrible engineering.