3 ms·
It's worth remembering that, because there were no Javascript or HTML APIs for many things people felt their pages needed, a huge portion of the web was loading
by nitwit005 7y ago
It's worth remembering that, because there were no Javascript or HTML APIs for many things people felt their pages needed, a huge portion of the web was loading up flash, silverlight, or java applets.
Now, maybe they never should have allowed Flash and friends, but the genie was well out of the bottle. You could either have HTML and JS based functionality, or the plugins.
- skunkpocalypse 7y agoWHATWG should have published a standard to replace Flash -- all the same goals as Flash, but a clean-slate standards-driven design. Instead they infected the HTML standard with everything Flash was being used for.
- zozbot234 7y agoUm, they did exactly that via HTML canvas. Replacing the main use cases for both Flash and Java applets.
- zmix 7y ago> It's worth remembering that, because there were no Javascript or HTML APIs for many things people felt their pages needed The OA states in his article, that he is fine with many of the new APIs. It's not HTML5 vs. XHTML, it's 'applified web' vs. 'document web'. And I agree.