3 ms·
> This destroys a non-technical user's grasp of the differences between static HTML and programatically manipulated HTML. I think this line says it all. Non-t
by aaron695 13y ago
> This destroys a non-technical user's grasp of the differences between static HTML and programatically manipulated HTML.
I think this line says it all.
Non-technical user don't even know what HTML is, the concept they'd ever "grasp of the differences between static HTML and programatically manipulated HTML"? Do these people live in the real world?
- slaxman 13y agowell said. The fault lies in assuming that the rest of the world works like the way we (hackers) do. The fact is that they do not. Further, many of end users actually do like some of those animations that we find shitty. JS makes the web feel responsive and interactive. I helps keep the user engaged with you site if used in the correct manner. Removing the option that easily disables it for a majority of users if the right step. Hackers will always find a way around it.
- dthunt 13y agoI will say this: it confuses the hell out of daihyou, who spends a lot of time on linkedin. One man's 'responsive and interactive' is another man's "Did it work?" I'm not going to make a value judgement on this bit. If snappy, responsive, and interactive are priorities, they should be handled in a way that doesn't involve opening the gates of hell and letting Javascript out. If the standards don't provide a clean way to do that that ensures accessibility and that pages don't discriminate against programmatic displays, then they damned well should so that we can exercise the hellspawn that is Javascript once and for bloody all.