Need advice about which tool to choose?Ask the StackShare community!
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.
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?
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 ?
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.
Pros of jQuery
- Cross-browser1.3K
- Dom manipulation957
- Power809
- Open source660
- Plugins610
- Easy459
- Popular395
- Feature-rich350
- Html5281
- Light weight227
- Simple93
- Great community84
- CSS3 Compliant79
- Mobile friendly69
- Fast67
- Intuitive43
- Swiss Army knife for webdev42
- Huge Community35
- Easy to learn11
- Clean code4
- Because of Ajax request :)3
- Powerful2
- Nice2
- Just awesome2
- Used everywhere2
- Improves productivity1
- Javascript1
- Easy Setup1
- Open Source, Simple, Easy Setup1
- It Just Works1
- Industry acceptance1
- Allows great manipulation of HTML and CSS1
- Widely Used1
- I love jQuery1
Pros of Vanilla.JS
- Web-components2
- Lightweight2
- NO CONVENTIONS1
- No buildtool overhead1
- Faster than any framework1
- Unopinionated1
- Easy to learn1
Sign up to add or upvote prosMake informed product decisions
Cons of jQuery
- Large size6
- Sometimes inconsistent API5
- Encourages DOM as primary data source5
- Live events is overly complex feature2
Cons of Vanilla.JS
- You need to build anything yourself2