3 ms·
More like progress is figuring out the common patterns and offering shortcuts for them. The querySelector api for example was born from jquery's popularity.
by rererereferred 2y ago
More like progress is figuring out the common patterns and offering shortcuts for them. The querySelector api for example was born from jquery's popularity.
- oneeyedpigeon 2y agoAnd it makes sense for those shortcuts, in general, to migrate 'up' the stack, JS -> CSS, JS+CSS -> HTML.
- wruza 2y agoReally? I always thought jQuery was just a shorthand for it cause it’s too long to type. And they really walked the DOM to look for an element? What an ugly runtime it was, ugh. https://stackoverflow.com/questions/39979816/how-was-jquery-selector-defined-before-queryselector-wasnt-available https://stackoverflow.com/questions/39979816/how-was-jquery-...
- hnbad 2y agoBefore `querySelectorAll` there was Sizzle, which was the selector engine that was eventually spun out of jQuery itself: https://github.com/jquery/sizzle https://github.com/jquery/sizzle If you think that's wild, before there were dev tools in every browser, there was only Firebug (yes, there was only `alert` before that, we didn't even have `console.log`): https://getfirebug.com/ https://getfirebug.com/