jQuery has been the de facto for normalization in the web industry for years now, and its relevance in recent iterations of both the web standard as well as browser support has been brought to question by many community members.
Anymore, it seems jQuery’s true purpose – to provide maximum compatibility with a wide array of browsers and to abstract otherwise arguably complex APIs behind a simple interface – has been blurring given the recent slew of W3C specification updates with the upbringing of HTML5.
Instead of saying why we use jQuery at Drake Cooper, I’d like to point out some common concerns when considering when not to use jQuery.
If there was anything that could undeniably be true without a single thread of doubt, jQuery is indeed very slow.
It’s worth pointing out that CSS is often hardware accelerated and many graphical operations are performed directly on the GPU, leaving the CPU more room to breathe.
Vanilla isn’t hard
One thing I’ve noticed is the continual surprise from our UX/front-end developers with how simple vanilla is compared to how it is perceived.
For example, one of the preliminary concerns with dropping jQuery was How can I easily query elements using selectors?
document.querySelector[All], of course! Oh, and it’s faster.
There were other concerns, such as easily adding events (through
Most other concerns centered around coding speed – that is, how easy it is to build up a page using jQuery vs. vanilla – also easily answerable by building up a simple code base to help you with any strenuous activity you perform frequently.
The unfortunate part about all of this – most convenient bits of code are targeted specifically for jQuery. This is one of the only reasons we’ve not dropped jQuery completely from Drake Cooper’s workflow.
Let’s get real
Alright, so jQuery is arguably unnecessary in most cases, and provides virtually no performance or usability enhancements.
That’s not to say, however, that jQuery doesn’t have a place. If a site needs to be supported on older browsers – namely IE8 and below – jQuery is the sensible choice. Since the demographic for these browsers, however, is so small, there is very little point in supporting them.
Further, jQuery supports certain things CSS hadn’t introduced until (sometimes recent revisions of) CSS3, such as animations and rotation. While Firefox and Chrome have undisputedly been quite good sports about supporting new specifications, Internet Explorer has always been a culprit for missing or sometimes incorrect functionality necessary for modern sites to function – often polyfilled by jQuery.
With that being said, Drake Cooper does not support IE8 or below. While it was an easy decision to make, it was one worth definitively making in a web design and interactive development environment. By throwing out this one browser, we’ve eliminated the need for many polyfills jQuery has provided us.
Ultimately, we do use jQuery for quick or presentational bits of sites here at Drake Cooper. However, our mindset does not center around jQuery, and we try to find every opportunity to not use it.
If you ask me, an interactive developer and programmer, jQuery is nothing but an impediment. That is why we don’t use jQuery at Drake Cooper.
DRAKE COOPER Contact: Lisa Hawkes, (208) 342-0925, email@example.com OUTSIDE Contact: Maya Meredith, (212) 255-0945, firstname.lastname@example.org BOISE, Idaho (October 2, 2014)…
Our Creative Advertising Services
Campaign Planning™ & Strategy
Brand & Sales Strategy, Research
Art, Story & Experiential
Copywriting, Design, Social, Content
UX & Technology
UX, UI, Development, Marketing Automation
SEO, SEM & Overall User Experience
Media Strategy, Planning & Buying
Media Strategy, Planning, Buying, Trafficking & Attribution
Data Insights & Analytics
Media Optimization, Trends, Forecasting, Testing
Photo & Video Production
Direction, Cinematography, Editing, Post