|
I've come to believe that, in retrospect, 'AJAX' was a mistake. For the first decade of the web, nearly all its functionality was implemented using HTML tags. What roles does the web serve that benefit humanity? Some of the most important are: 'literary', 'research', 'educational', 'financial service', 'commercial service', 'audio/video'. Then we have a 'typesetting/graphic-design' role, which is 99% of the reason the web 'requires' JS and CSS. As long as we were happy with a "one-size-fits-all" design, we could enable the other roles via (existing, and future) HTML tags alone (the way we did prior to the introduction of JS). Now, what are the trade-offs we make to gain the 'typesetting/graphic-design' role? They are a loss of: security, privacy, legibility, compatibility, accessibility, ease-of-use, and page load speed. To be fair, we also gain fantastic abilities for web developers to innovate, but we could probably find some workaround, without 'AJAX', to allow devs to experiment. The world would be better off, in may ways, if we scrapped the web's dynamic features, created a few new HTML tags, and re-implemented them using HTML alone. |
You also don't need JS to support it, although you may have to give up on the idea that your site has to look the same in all browsers, because not all browsers can do things like automatic hyphenation.
And frankly I am happy that I don't have to read source code in Courier just because it is the only available monospace font.