Search posts, tags, users, and pages
Listen kid, dig into react and you will find out that react will not work with Jquery as React itself is a view management lib and it would not like a s*it a*s library like Jquery interfering with it's work.. so, any implementation of JS that works with React HAS to be Jquery free.
React can work with jQuery but it is not best practice I suppose.
Do you know why it is not considered best practice?
S*hit a*s library? That's a bit harsh... We have evolved from jQuery sure, but it saved all of our s*hit a*ses for a long while there, champ. We should all kiss John Resig's s*it a*s at least once if you ask me.
Jason Knight.... Talk some sense into these people...
The reason I hate JQ is because I have never used it in my life. It just gave tons of functions that you would probably never use, increasing the size of the code base for no good reason. But of course, we all come from different background. I have had this fight with soooo many people that I have literally lost count. If you still feel JQ is the best thing that happened in your life, be my guest.
That fat bloated TRAIN WRECK of developer ineptitude is responsible for more broken accessibility on websites than most any other cause. EVERYTHING I've ever seen done in jQuery falls squarely into one of three categories:
1) stuff that would have been less code, simpler to code, or more efficient to code without it.
2) Stuff that's CSS' damned job!
3) Garbage that has ZERO damned business on a website in the first place.
That by itself MINIFIED and gzipped it is in the same ballbark that I would generally allow scripting in a template (at least my own, not counting social media stuff) to reach WITHOUT minification/compression? 100% grade A farm fresh derpitude!
As I'm always telling people the only thing you can learn from it is how NOT to use JavaScript -- and JUST like every other one of these stupid ignorant halfwit front-end "frameworks" the ONLY way you could think it made anything 'easier' or 'simpler' is a failure to know enough JavaScript to have any damned business using it in the first place!!!
Two thirds of its codebase is artsy-fartsy crap that only impresses script-kiddies and rubes, and does NOTHING but get in the way of usability and accessibility. All the claims of what it does makes little to no sense to me, as how it works is a convoluted pointlessly cryptic train wreck that just makes people work harder, not smarter... and when people talk about it helping work on the DOM, I genuinely HAVE ZERO DAMNED CLUE WHAT THE **** THEY'RE TALKING ABOUT, GIVEN IT SLOPS IN THE DUMBASS INNERHTML METHODOLOGY ALL OVER THE PLACE AND ENCOURAGES THE USE OF ENDLESS NODELISTS! THAT'S THE OPPOSITE OF WORKING WITH THE DOM!!!
Just look at the BS hoops you have to jump through just to get what vanilla JS these days can grab as firstElementChild.
I genuinely have to question the sanity -- much less intelligence -- of anyone who uses it by choice. JUST like other halfwit garbage like bootcrap, the only way you can see genuine benefit from its use is if you flat out do not know enough about HTML, CSS, or JavaScript to be using web technologies! No matter how much you may have deluded yourself into thinking you do.
It's not just a pile of manure, it's at least two metric tonnes of it -- enough to easily bury Biff's 1948 Ford Super De Luxe for good.