3 ms·
I just want to say that while a lot of people have browsers with JavaScript enabled you shouldn't use it for things that the browser does natively. Not just fo
by bobajeff 10y ago
I just want to say that while a lot of people have browsers with JavaScript enabled you shouldn't use it for things that the browser does natively.
Not just for performance reasons. But because that puts the burden of maintenance of those elements on the website.
It's a lot like how you shouldn't use fixed width and margins for pages. There are a lot of assumptions developers make when building these elements that can easily change and obsolete their work.
So unless you absolutely have to don't take on that burden.
- nomel 10y agoAny idea why this was put down? The concept of keeping critical functionality to "expertly maintained" libraries seems sane to me, otherwise we would all be writing our own encryption routines.
- abritinthebay 10y agoRight, I'm not disagreeing with that at all. I'm pointing out that a knee-jerk "doesn't work with JS" is irrelevant to 99% of web users. Be there are other considerations of course, like accessibility, UX consistency, etc (all of which ARE doable in JS if you have to) but that's not what I was responding to, was it?
- abritinthebay 10y agoRight, I'm not disagreeing with that at all. I'm pointing out that a knee-jerk "doesn't work with JS" is irrelevant to 99% of web users. Be there are other considerations of course, like accessibility, UX consistency, etc (all of which ARE doable in JS if you have to) but that's not what I was responding to, was it?