1. It's client-server all over again. But without the problems of deploying an application to thousands of desktops. 2. Web UIs are a mess. These arguments a

1. It's client-server all over again. But without the problems of deploying an application to thousands of desktops. 2. Web UIs are a mess. These arguments are the same for the desktop apps. Powerbuilder looks different than .NET looks different than Swing... Besides, maintaining an open stateful connection to a server is very very expensive and limits scalability. 3. Browser technologies are too limiting. Wrong! Having to go into the office because your desktop app is installed on the computer in your cube and you can't VPN is too limiting. Web apps enable the freedom to access information securely from anywhere much much easier than desktop apps. 4. The big vendors call the shots. A little bit of truth here. Browser incompatibilities are a real hurdle, but so are desktop incompatibilities. I'd rather solve incompatibilities between a few browsers (which in an organization is usually just /one/ corporate standard browser) than thousands of different desktop configurations: laptops for the execs, desktops for the front line, etc... 5. Should every employee have a browser? Just because you have a web browser installed doesn't mean it can browse the "web". Install a firewall or block problem domains -- all the cool corporations are doing it!