HTTP Clients #3: The Cost and Benefit of Fat

So. We’ve talked now about cost & benefit for thin-client, i.e. browser solutions. What are the cost & benefit of fat-client, i.e. app solutions? There is one primary cost for a fat client, as opposed to a thin, and it’s obvious: It doesn’t write-once-run-anywhere. Now a couple of things. We’ve already pointed out that a thin client doesn’t do that,…
Read More

HTTP Clients #2: The Cost of Thin

Yesterday, we started with thin (i.e. browser) clients versus fat (i.e. app) clients. We considered the alleged benefits of thin, which I believe we routinely overestimate. Today I want to talk about the costs, which I believe we routinely underestimate. I mentioned the other day how much I prefer a fat-client approach to today’s standard and largely unquestioned reliance on…
Read More

HTTP Clients #1: The Benefit of Thin?

I mentioned the other day how much I prefer a fat-client approach to today’s standard and largely unquestioned reliance on browser-based solutions. I want to step into it, even knowing I’m gonna get yelled at. Freely made admissions to start: 1) I admit there are situations where a browser is best. 2) I admit that some modern internet-stack environments are…
Read More