Need advice about which tool to choose?Ask the StackShare community!
ES6 vs jQuery: What are the differences?
Developers describe ES6 as "The next version of JavaScript". Goals for ECMAScript 2015 include providing better support for large applications, library creation, and for use of ECMAScript as a compilation target for other languages. Some of its major enhancements include modules, class declarations, lexical block scoping, iterators and generators, promises for asynchronous programming, destructuring patterns, and proper tail calls. On the other hand, jQuery is detailed as "The Write Less, Do More, JavaScript Library". jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML.
ES6 can be classified as a tool in the "Languages" category, while jQuery is grouped under "Javascript UI Libraries".
"ES6 code is shorter than traditional JS" is the primary reason why developers consider ES6 over the competitors, whereas "Cross-browser" was stated as the key factor in picking jQuery.
jQuery is an open source tool with 51.9K GitHub stars and 18.3K GitHub forks. Here's a link to jQuery's open source repository on GitHub.
Uber Technologies, Twitter, and reddit are some of the popular companies that use jQuery, whereas ES6 is used by Slack, StackShare, and ebay. jQuery has a broader approval, being mentioned in 4052 company stacks & 2611 developers stacks; compared to ES6, which is listed in 1462 company stacks and 1731 developer stacks.
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 ?
This post is a bit of an obvious one, as we have a web application, we obviously need to have HTML
and CSS
in our stack. Though specifically though, we can talk a bit about backward compatibility and the specific approaches we want to enforce in our codebase.
HTML
: Not much explanation here, you have to interact with HTML for a web app. We will stick to the latest standard: HTML 5
.
CSS
: Again if we want to style any of our components within he web, we have to use to style it. Though we will be taking advantage of JSS
in our code base and try to minimize the # of CSS stylesheets and include all our styling within the components themselves. This leaves the codebase much cleaner and makes it easier to find styles!
Babel
: We understand that not every browser is able to support the cool new features of the latest node/JS features (such as redue, filter, etc) seen in ES6
. We will make sure to have the correct Babel
configuration o make our application backward compatible.
Material UI (MUI)
: We need to make our user interface as intuitive and pretty as possible within his MVP, and the UI framework used by Google will provide us with exactly that. MUI provides pretty much all the UI components you would need and allows heavy customization as well. Its vast # of demos will allow us to add components quickly and not get too hung up on making UI components.
We will be using the latest version of create-react-app
which bundles most of the above along many necessary frameworks (e.g. Jest for testing) to get started quickly.
For our front-end, React is chosen because it is easy to develop with due to its reusable components and state functions, in addition to a lot of community support. Because React is popular, it would be easy to hire for it here at our company MusiCore. Our team also has experience with React already. React can be written with ES6 and ES6 has a lot of popularity and versatility when it comes to creating classes and efficient functions. Node.js will be used as a runtime environment to compile the code. Node.js also has many different types of open-source packages that can help automate some of the tasks we want to do for the application. CSS 3 will be used to style components and is the standard for that.
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.
Optimize-js
I will not describe this tool a lot here, because it's already good done by author on github
I just want to mention that this tool wrap up all immediately-invoked functions or likely-to-be-invoked functions in parentheses what is do a great optimization a JavaScript
file for faster initial execution and parsing (based on my experience).
The performance of application where I've introduced optimize-js
improved on 20% in a common (tested in Chrome
and IE11
).
- Clarification on Readme to the optimize-js
- Some of Nolan thoughts on the virtues of compile-time optimizations can be found in "Parens and Performance" – counterpost
Is it maintaining now? - Unfortunately, no (but feel free to send PR)
Pros of ES6
- ES6 code is shorter than traditional JS109
- Module System Standardized52
- Extremly compact2
- Destructuring Assignment2
Pros of jQuery
- Cross-browser1.3K
- Dom manipulation957
- Power809
- Open source660
- Plugins610
- Easy458
- Popular395
- Feature-rich350
- Html5281
- Light weight227
- Simple92
- 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
- Just awesome2
- Used everywhere2
- Powerful2
- Nice2
- Widely Used1
- Improves productivity1
- Open Source, Simple, Easy Setup1
- It Just Works1
- Industry acceptance1
- Allows great manipulation of HTML and CSS1
- Javascript1
- Easy Setup1
Sign up to add or upvote prosMake informed product decisions
Cons of ES6
- Suffers from baggage1
Cons of jQuery
- Large size6
- Sometimes inconsistent API5
- Encourages DOM as primary data source5
- Live events is overly complex feature2