4 ms·
> just as much on the tech churn treadmill. Really? I doubt you could run an app written for Android in 2010 (2.2 Froyo) today. But a website written in 2010 u
by TedDoesntTalk 6y ago
> just as much on the tech churn treadmill.
Really? I doubt you could run an app written for Android in 2010 (2.2 Froyo) today. But a website written in 2010 using HTML, Javascript, and CSS and no plugins will almost always work.
- ptx 6y agoI use a shopping list app[1] that was last updated in January 2011 (so pretty close to 2010) and still works fine. The UI is huge and blurry, but it works. [1] https://f-droid.org/app/caldwell.ben.trolly https://f-droid.org/app/caldwell.ben.trolly
- hajimemash 6y agoAintcha kinda makin' the opposition's point? That usage case is at a bare-minimum level of dead-simple and minimal-time-in-app usage. Any app with a more involved workflow would effectively be considered obsolete due to being so inferior.
- ptx 6y agoI don't know, I wasn't necessarily making a point, just giving a counter-example. And this simple app is hardly inferior - I use it because I like it.