I've worked on projects where that was the expectation; I've set that expectation for projects.

I've worked on projects where that was the expectation; I've set that expectation for projects. The reasoning has both been concrete/practical and philosophical (but still practical): * Mobile processing time is still costly in terms of battery life and performance. And the number of http calls (and their latency) also makes a difference in performance; SPAs tend to have smaller requests but larger numbers of them and it seems to me that's actually the opposite profile of what 3/4G cellular networks are good at. (And while this is all less true on the desktop I'm starting to find it annoying that we're nevertheless finding ways to make things choppy and slow on 2 GHz machines with operations not more complex than scrolling ). * This is more vague, but I find there's a discipline imposed in starting the conception of the app in terms of plain HTML/HTTP that seems to keep things better organized, while projects that start with a focus on a rich/heavy UI devolve into overspecific yet mixed concerns more quickly. This doesn't work for everything, since some apps just aren't about resources and media types. But honestly, your app probably is. :) * Being able to debug/autotest with something like curl is pretty nice.

Posted by wwweston on Jan 15, 2015, 12:04 AM

Tags

• ux (SaaS)

Related issues

• Some good points here, and I definitely hate the "unalive" movement but like someone else said, it has gone beyond self-censorship to in-...
• It’s hard to take the article seriously when there’s no real discussion about how consciousness is defined and it takes Anthropic’s views...
• you know what i hate?
• > I honestly do not understand why any average person would buy anything else than a macbook today.
• Codex App frequently freezes/stutters on Windows 11 Pro despite sufficient system resources
• Add "Basic" and "Standard" plans