If you lose performance on every single request, scale will only make you lose more. But yes, you can offload a tiny amount of server-side processing onto the client side. If that makes a difference in your costs ...
No I can't say then go for it. What you say is bullshit. Offloading string mangling to the client at the cost of doing extra requests is absurd.
We established that a single request (ie. directly filled in page) is going to be faster than javascript doing requests. You appear to agree. The only thing scale will bring is a bigger difference.
Javascript/AJAX is simply a manifestation of "Worse is better":
1) programmers start making websites. Good ones, and bad ones.
2) we see lots of examples of badly programmed server-side programming.
3) "we must fix this", and so now we do client side programming
4) incredible amounts of examples of bad client-side programming
No I can't say then go for it. What you say is bullshit. Offloading string mangling to the client at the cost of doing extra requests is absurd.
We established that a single request (ie. directly filled in page) is going to be faster than javascript doing requests. You appear to agree. The only thing scale will bring is a bigger difference.
Javascript/AJAX is simply a manifestation of "Worse is better":
1) programmers start making websites. Good ones, and bad ones.
2) we see lots of examples of badly programmed server-side programming.
3) "we must fix this", and so now we do client side programming
4) incredible amounts of examples of bad client-side programming