HTTP Clients #3: The Cost and Benefit of Fat

This entry is part [part not set] of 3 in the series HTTP Clients

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, either. But — play fair — thin clients usually run at least "okay" in more places than fat ones do. […]

HTTP Clients #3: The Cost and Benefit of Fat See Full Post