4 ms·
As someone who experienced the rise of JavaScript, CSS and modern frontend frameworks, your comment gives me a chuckle because I'm pretty sure using JavaScript
by hnbad 2y ago
As someone who experienced the rise of JavaScript, CSS and modern frontend frameworks, your comment gives me a chuckle because I'm pretty sure using JavaScript for hover effects pre-dates the ability to do that reliably using CSS.
- oneeyedpigeon 2y agoIsn't this just pointing out that progress = functional -> declarative?
- rererereferred 2y agoMore 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/
- achairapart 2y agoYes, but it was called DHTML back then! Added: And it was not a deliberate choice but kind of a necessity.
- rererereferred 2y agoI remember using Flash for hover effects. People complain we are in a cycle reinventing the wheel but I rather like the current wheel over the old one.