3 ms·

This view that you don’t need JS and can do most things natively is tired and screams of old timers trying to cling on to the past, when web pages didn’t have r

by bhobs 4y ago

This view that you don’t need JS and can do most things natively is tired and screams of old timers trying to cling on to the past, when web pages didn’t have rich user interactions and good UX. Sure, you can build forms that perform full page refreshes, but ajax requests offer a better user experience.

uallo 4y ago
Native dropdowns have much (much!) better UX and accessibility than most custom dropdowns built with JavaScript. Same goes for native form validation. And there are many more examples. Using JavaScript does not necessarily improve UX. Use the platform where it makes sense. Extend it with JavaScript where needed. Make it work for everybody and make it better for capable browsers. That is called progressive enhancement. OP did not say that you may never use JavaScript. Just be mindful about it when you do.
- amelius 4y ago
  You can say the same about computers in general. No computer is preferable over having to use one.
krono 4y ago
When someone has just barely crossed the "hello world" stage, I don't think they should be thinking about asynchronous XHR requests, or be pulling up user experience research to find the optimal shade of red for making input validation errors appear less aggressive to middle aged women with a bachelor degree in communications who are part-time employed in marketing. Let's start with getting data from the form to your back-end, and once we've got those must-have basics down, then we can start introducing the nice-to-have bits.
bigDinosaur 4y ago
I consistently have a more pleasant time with the well-designed, minimal JS websites (which are now a rarity) than even the better designed websites which heavily use JS. And my job is allegedly to 'improve' the internet with more JS.
chrisweekly 4y ago
See https://remix.run https://remix.run for a clear demonstration of "best of both worlds".

by bhobs 4y ago

uallo 4y ago

Native dropdowns have much (much!) better UX and accessibility than most custom dropdowns built with JavaScript. Same goes for native form validation. And there are many more examples. Using JavaScript does not necessarily improve UX. Use the platform where it makes sense. Extend it with JavaScript where needed. Make it work for everybody and make it better for capable browsers. That is called progressive enhancement. OP did not say that you may never use JavaScript. Just be mindful about it when you do.

amelius 4y ago
You can say the same about computers in general. No computer is preferable over having to use one.

krono 4y ago

When someone has just barely crossed the "hello world" stage, I don't think they should be thinking about asynchronous XHR requests, or be pulling up user experience research to find the optimal shade of red for making input validation errors appear less aggressive to middle aged women with a bachelor degree in communications who are part-time employed in marketing. Let's start with getting data from the form to your back-end, and once we've got those must-have basics down, then we can start introducing the nice-to-have bits.

bigDinosaur 4y ago

I consistently have a more pleasant time with the well-designed, minimal JS websites (which are now a rarity) than even the better designed websites which heavily use JS. And my job is allegedly to 'improve' the internet with more JS.

chrisweekly 4y ago

See https://remix.run https://remix.run for a clear demonstration of "best of both worlds".