4 ms·
Practical for front-end devs, not so much for us users who have to live with laughably shitty js-reimplementations of decades old built-in browser functionalit
by cannabis_sam 5y ago
Practical for front-end devs, not so much for us users who have to live with laughably shitty js-reimplementations of decades old built-in browser functionality…
Heaven forbid you’re on a shitty internet connection, these inane js-behemoths just die from a dropped tcp connection, since they’re built on the most optimistic assumptions about network connectivity.
I remember when accessibility was a part of web development, but I guess the ROI was to low.
- jaredgorski 5y agoI did mention that our clients are enterprise-level. But I did fail to address a more general decision-making process regarding choosing frontend architecture. If I did (and I probably will soon), I would talk a lot about the egregious initial load times on too many blogs that roll crazy dynamic tools for what should be a completely static site.
- cannabis_sam 5y agoYeah, I’m sorry. Looking back at it, that comment was written in general exasperation with the current state of the web, not really at you in particular.
- jaredgorski 5y agoYour exasperation is absolutely shared. Thanks for engaging
- cannabis_sam 5y agoThanks!