Name: Anonymous 2015-06-26 4:55
Unless the software you want on the web is a UI in itself, like Google Docs, you don't actually need javashit. Minimize its use totally.
The ``web app'' can still by dynamic--just serve everything from the server as nice compact html files. The user changes the state of something, serve a new html page.
``B-b-bbbut muh AJAX calls can make it more like a real program!'' Forget it. The only reason you need to make AJAX calls when the user changes state and then modify the original page based on the response, is because loading a new page with all your javashit will take forever. This is the solution to a problem that's caused by itself: javashit. If you would just remove all <script> tags and serve plain HTML and CSS, loading a new page would take just as long or less than the AJAX query. Besides, a new page for a new state in your application is much more intuitive.
It's time to end the cargo cult mentality of making websites that rely on javashit. When it comes to websites, you're sacrificing the most important resource (network resources) for the sake of some eye candy and phony UX bells and whistles, which users don't really care about.
Craigslist and Amazon are one of the few websites who know what they're doing. They both work very well without javascript. It automatically works perfectly well on mobile devices with very little customization only for mobile, because it's regular html that has worked forever. The big problem about browser and device compatibility in the javashit world is nullified by simply not using javashit.
Using javashit to make a ``web app'' introduces massive complexity. The worst part is that it's totally unnecessary, nothing but an exercise in vanity.
The ``web app'' can still by dynamic--just serve everything from the server as nice compact html files. The user changes the state of something, serve a new html page.
``B-b-bbbut muh AJAX calls can make it more like a real program!'' Forget it. The only reason you need to make AJAX calls when the user changes state and then modify the original page based on the response, is because loading a new page with all your javashit will take forever. This is the solution to a problem that's caused by itself: javashit. If you would just remove all <script> tags and serve plain HTML and CSS, loading a new page would take just as long or less than the AJAX query. Besides, a new page for a new state in your application is much more intuitive.
It's time to end the cargo cult mentality of making websites that rely on javashit. When it comes to websites, you're sacrificing the most important resource (network resources) for the sake of some eye candy and phony UX bells and whistles, which users don't really care about.
Craigslist and Amazon are one of the few websites who know what they're doing. They both work very well without javascript. It automatically works perfectly well on mobile devices with very little customization only for mobile, because it's regular html that has worked forever. The big problem about browser and device compatibility in the javashit world is nullified by simply not using javashit.
Using javashit to make a ``web app'' introduces massive complexity. The worst part is that it's totally unnecessary, nothing but an exercise in vanity.