>>10548the only legitimate use of javascript i know of is twine games. (i.e. empowering the technically unskilled) so far as i am concerned, everything else should be outlawed. if you can parse CSS with your eyes, you don't need to suck up memory with your shit javascript tracking. do the website properly.
(there is no empirical data to back it up, but i guarantee that in aggregate people who make twine games probably make better websites than people who don't. purely because they fall into the kind of demographic that makes a cute neocities full of glitter rather than being a professional web designer who manages to make a site that serves 500 words waste 15 megabytes.)
i could develop on this and a general distaste for bloat and so on, but really my position isn't so much a technical one as a social one: i say knock down a core pillar of the web as it stands today and just see what happens because the consequences couldn't possibly be worse than what we have now. this is of course a fantasy: you cannot send an army to destroy javascript. i have to confess this to myself, rather than proposing this or that protocol. all that can be achieved is screaming at the wind about how much i hate the modern web and then tithing my conscience by leaving positive feedback on obscure, marginally interactive short stories.