5 ms·
It was exactly the same with jQuery - there were a legion of people (older than me!) who could only "code" with jQuery. They'd never seen window.getElementById(
by radicalbyte 5y ago
It was exactly the same with jQuery - there were a legion of people (older than me!) who could only "code" with jQuery. They'd never seen window.getElementById().
- kolanos 5y ago> It was exactly the same with jQuery - there were a legion of people (older than me!) who could only "code" with jQuery. They'd never seen window.getElementById(). No, they'd seen window.getElementById() but quickly realized that DOM API manipulation wasn't consistent between browsers. The whole reason jQuery was created in the first place was to abstract these browser inconsistencies away into a single API.
- bdcravens 5y agoAs someone who started writing Javascript in 1997, when it came around, I would default to jQuery unless I had a very good reason not to.
- jacobsenscott 5y agojQuery still provides an objectively superior (more expressive, concise, and compatible) API for the dom. Yes, the cut an paste "you don't need jquery" solutions work 90% of the time. But jquery works 99.99% of the time and cover more of the gnarly edge cases that exist even on modern browsers.