3 ms·
Yes, very true, but I'm not sure that this necessarily precludes good/fast/usable interfaces. Imagine if instead of building apps inside a browser, you instead
by brandur 10y ago
Yes, very true, but I'm not sure that this necessarily precludes good/fast/usable interfaces.
Imagine if instead of building apps inside a browser, you instead have a good OS framework that allows you to build a native app for which you can ship updates easily and which simply talks to your backend's API. It would be a very similar model to what most of us use today in our browsers, but would open a lot of doors around what we're currently getting wrong with interfaces on the web.
It also already exists in a few limited forms: apps on iOS or Android for example.
- 5ilv3r 10y agoNeeding to ship updates frequently is the root of the problem, in my mind. If people would just build something they could stand behind, and not rely on any environmental flux corrections to stay useful, software would go back to being quick and minimal. coughhttpscough
- brandur 10y agoYeah, I think there's some truth to this. When I look at games in particular, I'm amazed that you can have AAA titles that get hotfixes for bad bugs on pretty much the day they're released. This is made possible by sophisticated content distribution networks like Playstation's. Twenty years ago your pressed a master disk, crossed your fingers, and tossed it to the wolves. If there was ever a serious problem discovered after release, it would be a huge hit to your bottom line to ever have to try and recall everything that went out. Testing must have been much more comprehensive before to make the old system workable.