Many here are emphasizing the rise of client-side Javascript methodologies and I would like to play Devil's advocate. Instead I argue that client-side solutions

Many here are emphasizing the rise of client-side Javascript methodologies and I would like to play Devil's advocate. Instead I argue that client-side solutions will fade because they are largely unnecessary. Desktops today have multiple CPUs and high bandwidth. But hand-held devices do not, and that is the sector expected to grow faster. The same solutions that worked on a desktop yesterday with dial-up are needed for hand-held devices tomorrow. Yet, as wifi proliferates, bandwidth increases and latency decreases, the distinction between server and client fades and where processing occurs becomes less important. The least expensive solution will likely prevail. It seems that server-side centralization of processing is more likely both in the short and long run, despite the current plethora of client-side tools, frameworks and methodologies. My assumptions include the first 4 of the "8 Fallacies of Distributed Computing" (below). But my belief is that market forces will drive acceptance in hand-helds of what has already been accepted in cellphones (that is, inexpensive, unreliable, insecure, limited-bandwidth solutions), and simultaneously drive network solution providers to more reliable, secure, higher-bandwith capability and so those maxims no longer fully apply (or, better said, the customer no longer cares). Note: The 8 Fallacies of Distributed Computing: 1. The network is reliable 2. Latency is zero 3. Bandwidth is infinite 4. The network is secure 5. Topology doesn't change 6. There is one administrator 7. Transport cost is zero 8. The network is homogeneous.