Comment by Jason Knight on "Which is the best way to keep on learning React once you are not a beginner?"

Learn accessibility, learn to do it without the stupid framework, that way you can recognize how much the framework nonsense has saddled you up and taking you for a ride by teaching you bad habits and resulting in websites and interfaces that are a giant middle finger to user with accessibility needs, and how 80%+ of what you've done with the TRAIN WRECK of developer ineptitude has little business being done from JavaScript in the first place!

Seriously, if you think React is something to be used, you likely don't know enough about HTML, CSS, or JavaScript in the first place to be using it.

Yeah sure, cause every site should be built on vanilla JS. We never need any frameworks to assist or ease the development of certain functionality, like a WebVR framework, or combining React with a flat-file structure like Gatsby.

Yeah I could code all these things myself from scratch or try to find vanilla versions, and I'll quickly discover why people made the frameworks in the first place. There's no need to reinvent the wheel.

Or I could code some server-side React using Express, something HTML/CSS/JS will never be able to do without server side assistance (PHP, Rails, etc).

Gotta chill out with all that hate bro. People won't listen to your best practices if they're laced with insulting assumptions, or if they're just flat out wrong.

I've seen you say similar things when any JavaScript library/framework is mentioned, Jason. Can you be a bit more specific about how using these frameworks degrades accessibility? Examples would be nice to see.

Aaron Cooper Do pages built with it work scripting off, yes or no?

If no, you have your answer. If you question why that's so important:

addons.mozilla.org/en-US/firefox/addon/noscript

ghostery.com

chrome.google.com/webstore/detail/scriptsafe/oiig…

cbc.ca/news/technology/crtc-review-differential-p…

... and it's becoming REALLY popular on phones because for all the CLAIMS of such techniques saving bandwidth, it's usually BS since if people would STOP writing two to ten times the HTML they need, STOP adding MEGABYTES of scripting to pages no even delivering 5k of plaintext and a half dozen content issues, and bothered leveraging caching and pre-caching through the use of monlithic stylesheets and scripts, they wouldn't be diving for the "gee ain't it neat" JS for nothing and your scripts for free.

That ain't workin', that's not how you do it.

Search Hashnode