Overview

jQuery

Stacks194.7K

Followers70.6K

Votes6.6K

GitHub Stars59.6K

Forks20.5K

Vanilla.JS

Stacks82

Followers85

Votes9

Vanilla.JS vs jQuery: What are the differences?

Key Differences between Vanilla.JS and jQuery

Vanilla.JS is a term used to refer to pure JavaScript without any external dependencies, libraries, or frameworks. On the other hand, jQuery is a fast, small, and feature-rich JavaScript library.

1. Syntax and Code Length: Vanilla.JS code tends to have longer syntax, which can make the code more verbose. jQuery, on the other hand, provides a shorter and more concise syntax, allowing developers to write code in a more compact manner.

2. DOM Manipulation: Vanilla.JS uses the built-in methods and properties provided by the browser to manipulate the Document Object Model (DOM). jQuery simplifies DOM manipulation by providing a set of cross-browser compatible methods and functions that abstract away the complexities of working directly with the DOM.

3. Ajax and XMLHttpRequest: Vanilla.JS requires the use of the XMLHttpRequest object to make Ajax requests, which involves more manual coding. jQuery simplifies Ajax requests by providing an easy-to-use Ajax method with built-in features like automatic serialization, error handling, and support for various data formats.

4. Event Handling: Vanilla.JS uses the addEventListener method to attach event handlers to elements, which can result in more code for handling events. In contrast, jQuery provides a unified event handling API that simplifies attaching and detaching event handlers, as well as handling events across different browsers.

5. Browser Compatibility: Vanilla.JS leverages the native browser features, so it is inherently compatible with all modern browsers. jQuery, on the other hand, abstracts away browser differences and provides a consistent API, ensuring compatibility across multiple browsers and versions.

6. Performance and Size: Vanilla.JS code can be more optimized in terms of performance and can result in smaller file sizes compared to using jQuery. jQuery's extensive feature set and compatibility layer come at the cost of some performance overhead and larger file size.

In Summary, Vanilla.JS offers a more lightweight and optimized approach to JavaScript development, while jQuery provides a rich set of features and simplifies common tasks like DOM manipulation and Ajax requests.

Advice on jQuery, Vanilla.JS

Malek

Web developer at Quicktext

Mar 28, 2020

Decided

The project is a web gadget previously made using vanilla script and JQuery, It is a part of the "Quicktext" platform and offers an in-app live & customizable messaging widget. We made that remake with React eco-system and Typescript and we're so far happy with results. We gained tons of TS features, React scaling & re-usabilities capabilities and much more!

What do you think?

244k views244k

Comments

kazi

CTO at Blubird Interactive Ltd.

Mar 11, 2020

Decided

I've an eCommerce platform building using Laravel, MySQL and jQuery. It's working good and if anyone become interested, I just deploy the entire source cod e in environment / Hosting. This is not a good model of course. Because everyone ask for small or large amount of change and I had to do this. Imagine when there will be 100 separate deploy and I had to manage 100 separate source. So How do I make my system architecture so that I'll have a core / base source code. To make any any change / update on specific deployment, it will be theme / plugin / extension based . Also if I introduce an API layer then I could handle the Web, Mobile App and POS as well ? Is the API should be part of source code or a individual single API and all the deployment will use that API ?

115k views115k

Comments

Manatsawin

Jan 19, 2020

Decided

When I started TipMe, I thought about using React frontend. At the end, plain, simple jQuery won.

I had to build this iteration of the site fast and by using jQuery I could keep using Django as a full stack development tool. One important point is Django form (combined with Django Bootstrap3) means that I don't have to reinvent form rendering again, which will be the case with React.

Over time, more interactivity seeped into the site and React components start making its way into the codebase.

I now wish the site is built using React so that I could add more user friendly interfaces easier (no more fuddling with server states) but I would still say jQuery helped me get past those early days.

225k views225k

Comments

Detailed Comparison

jQuery	Vanilla.JS
jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML.	It is a fast and cross-platform framework for building incredible, powerful JavaScript applications. it is the most lightweight framework available anywhere.
Statistics
GitHub Stars 59.6K	GitHub Stars -
GitHub Forks 20.5K	GitHub Forks -
Stacks 194.7K	Stacks 82
Followers 70.6K	Followers 85
Votes 6.6K	Votes 9
Pros & Cons
Pros 1263 Cross-browser 957 Dom manipulation 809 Power 660 Open source 610 Plugins Cons 6 Large size 5 Sometimes inconsistent API 5 Encourages DOM as primary data source 2 Live events is overly complex feature	Pros 2 Lightweight 2 Web-components 1 Unopinionated 1 Easy to learn 1 Faster than any framework Cons 2 You need to build anything yourself

What are some alternatives to jQuery, Vanilla.JS?

AngularJS

AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.

React

Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.

Vue.js

It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.

jQuery UI

Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice.

Svelte

If you've ever built a JavaScript application, the chances are you've encountered – or at least heard of – frameworks like React, Angular, Vue and Ractive. Like Svelte, these tools all share a goal of making it easy to build slick interactive user interfaces. Rather than interpreting your application code at run time, your app is converted into ideal JavaScript at build time. That means you don't pay the performance cost of the framework's abstractions, or incur a penalty when your app first loads.

Flux

Flux is the application architecture that Facebook uses for building client-side web applications. It complements React's composable view components by utilizing a unidirectional data flow. It's more of a pattern rather than a formal framework, and you can start using Flux immediately without a lot of new code.

Famo.us

Famo.us is a free and open source JavaScript platform for building mobile apps and desktop experiences. What makes Famo.us unique is its JavaScript rendering engine and 3D physics engine that gives developers the power and tools to build native quality apps and animations using pure JavaScript.

Riot

Riot brings custom tags to all browsers. Think React + Polymer but with enjoyable syntax and a small learning curve.

Marko

Marko is a really fast and lightweight HTML-based templating engine that compiles templates to readable Node.js-compatible JavaScript modules, and it works on the server and in the browser. It supports streaming, async rendering and custom tags.

Kendo UI

Fast, light, complete: 70+ jQuery-based UI widgets in one powerful toolset. AngularJS integration, Bootstrap support, mobile controls, offline data solution.