2 ms·
Sure, 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
by mindslight 5y ago
Sure, 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.
- pjmlp 5y agoAlthough most of my work is Web development related, I also share the same opinion, we should have stayed with HTML 4 and do everything else with native apps and networking protocols. Unfortunely only a couple of water drops in this ocean share this opinion.
- eternityforest 5y agoI like the touchscreen model a LOT more than the old button model. There's one specific category of things that would be very well suited to a non-browser device, and that's IoT control, where you want something cheap enough to leave several around the house, drop-proof, with physical buttons. But the ideal for that would be more like a calculator with Wi-Fi and rotary encoders than a phone. Webapps could very easily be local first if they would hurry up and give us a non-nerfed(By certificate expiration) version of Signed Web Bundles. Chrome OS had a great idea with real local apps without as much web sandboxing, but developed with web tech to make them very easy to develop.