I have not been in touch with the front-end for a long time or a short time. I started 12 years ago. I practiced in Baidu at the beginning of 2014. I formally took part in the work in No. 14 middle school. I counted four years as a whole. However, the changes in the front end over the past four years have left many people confused.
Yesterday, I also sent a message, joking that jQuery is a tough community. Someone left a message asking why I said that.
I remember that when I first entered the front-end pit, jQuery was extremely popular, and the related books in the library were everywhere. The articles in the blog park were mostly introduced like stars, and jQuery plug-ins were all over the place, which was unprecedented. However, with the rise of multi-terminal devices and the growing demand for interfaces, jQuery is almost incompetent for daily development. Often, we see a bunch of jQuery components with poor performance on the page with slow loading, which are randomly put together. That scene is like entering a room that hasn't been cleaned for a long time, with stink and dust.
The front end is a species that likes to invent and solve problems. It does messy work, but it highlights its neatness in front of the user's perspective. From colorful components to engineering, componentization, modularization, and then back to the evolution of language itself, followed by a new round of change. Technology is changing, community is also changing, community is just a container of technology evolution, the end of technology is to return to business.
There are too many problems in the business, and there are more solutions. Every short period of time, the front-end will pop up with several new terms. Take apart the words to see if you know each letter, but put them together, you can only stare at your nose. No matter how much effort we put in and how much time we put in, new technology can never be learned completely and thoroughly. After learning thoroughly, we find that there is no practice. So more and more front-end began to hesitate, "did I deviate?" "Do you want to learn this?" "I just heard how the technology was eliminated." "How do I feel half a century behind when I go out for a tour?".
Yes, this is the current situation of the front-end circle. Five years ago, you could say that the front-end was superficial, but today - you can still say that A kind of ——The front-end knowledge volume has risen a step, but what we do still remains unchanged, cut! Page! Noodles! But we invented more and more rich page cutting tools, let the operation help us cut, let the program help us cut, let the machine help us cut.
At the same time of page cutting, our functions have also changed. We need to master more tools and more languages. From the client side to the server side or even the operation and maintenance level, from the front-end resources to the product leader, we can play games with the operation and product manager. We can even provide play methods, they jump in and play.
The front end has become a lot fuller in recent years, and there are more directions to go in. Wireless, node, react like, modularization, engineering and so on, the concept of "front-end domain" has begun to emerge. It is no longer a general HTML / CSS / JavaScript hodgepodge. Each domain has its own experts, and each domain has its own research methods. So there are a lot of opportunities and more interesting in the front-end. In fact, the WYSIWYG development of the front-end is a kind of interest in itself.
There are also many people who are constantly creating territory for the front-end circle and knowledge boundary, such as docker, HTTPS, automation, operation and maintenance, etc., and even directly cross-border cross-border cross language and other directions.
The front end evolves rapidly and violently, and it is important to find a place of its own.
So at the end of the article, a series of questions are raised. What have you experienced in the long history of front-end development? What did you learn? What level do you belong to? Where are you going?