11–20 of 156 posts
I'm surprised this needs jQuery. What this seems to be is a simple script that fetches a resource and places it into an element. I really feel opposed to adding more dependencies where they aren't required. That could be written without jQuery or this library fairly easily.
I'm surprised this needs jQuery. What this seems to be is a simple script that fetches a resource and places it into an element. I really feel opposed to adding more dependencies where they aren't required. That could be written without jQuery or this library fairly easily.
I am by no means a js expert, but doesn't jquery essentially act as an abstraction layer to smooth over differences in browser behavior?
I love that you can use this without having to build anything with babel/webpack. Given the scope of my web apps, anything that transpiles or mutates my sourcecode is a non starter because it makes debugging it weird since I'm not looking at my own code anymore.
I'm surprised this needs jQuery. What this seems to be is a simple script that fetches a resource and places it into an element. I really feel opposed to adding more dependencies where they aren't required. That could be written without jQuery or this library fairly easily.
I am by no means a js expert, but doesn't jquery essentially act as an abstraction layer to smooth over differences in browser behavior?
Earlier quoted context omitted.
I am by no means a js expert, but doesn't jquery essentially act as an abstraction layer to smooth over differences in browser behavior?
That was the one of the original use cases for jQuery, but browsers have gotten more compatible recently, so you may not need it anymore.
Intercooler.js makes them seem a little more "built in" to html, which I like.