Conversation:
Notices
-
♻ @kat: "Also, surely asking the client to run the code to build the pages is better design than making everything happen server side." That may be true if you're running an underpowered server that can't generate pages, but not for the user with a lightweight browser. Using #Javascript as the sole means to present content breaks the model of Content={text;video;audio}, Semantic…
-
@kat And then there's the whole security issue that @roland touched on -- I don't want some arbitrary web site running executable code on my computer. And when that #Javascript gets pulled in from multiple sources it's easy (but wrong) to just allow the entire page to run all the scripts it wants, leaving the user vulnerable to all the Javascript that comes from shady repositories or that's embedded in malcious ads.
-
And before I forget, this entire thread needs to be tagged with #Javascrippled