When I first started learning about the front end, ONE of my must-read books was called The Art of JavaScript DOM Programming. Powerful selectors, easy to use chain calls, rich plug-ins, occupied their front-end vision for a long time. Then in order to understand the principle of it, to read part of the source code, package their own plug-ins, read JavaScript Advanced Programming to understand some deeper language mechanism.

Then I came to AngularJS (1.x), which was my first experience with a relatively engineering-minded front-end project. Later, Vue and React gradually became the mainstream, forming a three-way confrontation. There was even a time when everyone was proud to despise jQuery. The productivity changes that data-driven thinking brings to the front end are huge, but that doesn’t mean that jQuery, which once ruled the front end, doesn’t have its place. Today, there are still a lot of projects that need to be maintained using jQuery, many simple demonstration projects may be faster and easier to use jQuery.

From jQuery’s perspective, the main problem I understand it solves is to encapsulate browser differences so that front-end developers don’t have to dig into the minuses of browser implementation. But as THE DOM API continues to evolve and unify, and as mobile becomes all the rage, its value continues to decline.

From the point of view of the project, it is difficult to go back to jQuery for the technical selection of the new project, which leads to the neglect of jQuery skills.

From the perspective of recruitment, the most common word in JD is the mastery of the three frames, which unconsciously allows graduates or applicants to learn more knowledge related to the frame.

From a personal point of view, jQuery is not a very difficult stack to master and should be one of the necessary skills for front-end developers. The pursuit of short and quick small projects is still practical. Similarly, if you practice the jQuery stack, you can better understand the reasons for the framework and the pain points to solve.

Finally, post a simple understanding of their own front-end development, welcome to be corrected.