The thing that holds back the Thin-Client idea is the "All-your-eggs-in-one-basket" problem. The same thing will always hamper computing via Internet.
In a Thin-Client atmosphere, if there is a catostrophic failure of the supporting server(s), whether that be hardware failure, software failure, power failure, whatever your entire work-force goes down.
In a Fat-Client atmosphere when a machine goes down, it affects ONE person, and the rest never know it happened.
A good example is MS Office. It can be run from the server, but hardly anyone does it. What's better, an Office Software failure taking out hundreds or thousands of workers, or just one?
I like thin-client technology for _some_ services, but for the true office grunt-work I'd never even consider it.
TL
|