3 ms·
Fat client apps are fantastic for making some kinds of UI interactions trivial. The simplest example is the checkout form, or any kind of wizard linking multip
by arohner 14y ago
Fat client apps are fantastic for making some kinds of UI interactions trivial.
The simplest example is the checkout form, or any kind of wizard linking multiple pages together. In a fat client app, all state for all N pages of your checkout cart are in the same page, with 5 lines of code to switch between them. Doing that in standard MVC "fat server" model is annoying, and about 10x more code.
> Why does the world want app-ify everything?
Think about GUI applications pre-web. They weren't written as servers that generate PDFs, with an embedded scripting language. The current webapp technology stack is a complete accident, and if we had actually sat down to design the "optimal" stack, it would look nothing like what we have.
- jarcoal 14y agoI completely agree with you that in some (many) cases it's useful. But your checkout example proves my point; you wouldn't want a bot crawling through there. Bots should be crawling content-rich pages (blogs, articles, marketing pages), and IMO those should rarely be handled by fat clients.