More and more developers join the front-end development team. However, the front-end knowledge is constantly updated, and everyone's understanding of it is also different. Today, I will explain to you the seven major misunderstandings of the web front-end.
Misunderstanding 1: The front end is just JavaScript
But what I want to say is: the front end is not just JS.
What is front-end development? I think that all work that aims at presentation is front-end development work. In front-end development, in addition to JS, there are many things that need to be mastered, such as browser principles, html5, css3, etc. When I was interviewing someone before, I asked him how to make a turntable on the touch screen. He shook his head. I took a step back and talked to him about your thoughts. He thought for a while, but still wouldn't.
Making a turntable may seem simple, but it represents a comprehensive application of front-end knowledge. You have no experience in touch screen development, CSS3 or canvas, and web page optimization. The front-end is an application of comprehensive technology, and only JS cannot solve the problem.
Misunderstanding 2: I hold everything now, no need to learn new things
Among the people I met, 60% had no actual working experience in h5 and CSS3, and even only heard some terms without researching them. Ask them why, most of the answers are not available for the previous work, and a small part of the answers have no time. When asked about the implementation of some animations, some interviewees are still using the CSS2 properties of the DOM to implement them frequently.
The reason for this situation may be related to the content of the work. At present, some mobile web pages in China are quite satisfactory, and product managers have few unconventional requirements for front-end implementation. The task of some front-end developers is to present the back-end data, which can indeed be achieved with CSS2. But these are not reasons not to learn new technologies, and one day they will be eliminated.
Misunderstanding 3: The front-end does not need to understand the back-end knowledge
Also, get the front end well on the front end and do what the back end does.
But the industry is developing, and the front-end functions are getting stronger. Off-line databases can provide data storage and management functions, but can it be fun to write SQL statements? WebSocket can provide instant communication, but I don’t know the difference between socket and WebSocket. Can it be built together with back-end development (many back-end development only uses socket technology)? Speeding up page display is not just about analyzing the front-end, but also considering the back-end So, the use of back-end technologies such as keep alive and caching can make the page open faster.
Misunderstanding 4: I think it’s so difficult for the boss to ask for it.
Don't exclude their unconventional needs, their strange needs may become an important competitiveness of the company. (Well, this point is switched to the perspective of the company operator.) Users are paying more and more attention to performance effects. Stop sending users with simple list pages and details pages. They may become because of a good user experience. Loyal users of the site.
When encountering unconventional needs, first think about how to use front-end knowledge to achieve it. If you can't figure it out, discuss it with your peers. In short, it is the developer's responsibility to realize the requirement. Don't say that we can't realize this requirement.
Misunderstanding 5: Regardless of other circumstances, the page will be fine
Most of the front-end rendering uses DOM, but there will be performance problems if DOM is used too much. Now it is very popular to pull up and load more on the bottom of the list page, but few front-ends pay attention to the extreme problem of loading. If I pull down a page many times and load thousands of DOMs, what will happen? The answer is that the page responds slowly, but the browser crashes.
Another example: LocalStorage is really convenient to use. Many companies rely heavily on it for the front-end, and even well-known front-end development frameworks rely on it. But it has a shortcoming-there are capacity limitations (2.6M-10M), we have to consider extreme cases, how to deal with when the LocalStorage space is almost full. Or avoid this extreme situation in the architecture.
Misunderstanding 6: The page is shown to the user, as long as the user can use it
It’s not just users who can see your page, but also robots.
Web App has been coveting the position of Native App, and there is no difference between some Web App and Native App. Web App is very popular, and various front-end MVC frameworks are also popular, but they all have a problem. It is almost impossible to do SEO because search engines ignore JS.
Traffic is the foundation of an enterprise. A good SEO can attract a lot of traffic, so the front-end still has to consider SEO issues.
Misunderstanding 7: Do not use/do not promote new technology
God gave you a pair of wings, but you grilled them.
Ask yourself a few questions. Does the webpage use CSS3 animation? Does the webpage support multi-touch operation? Proximity sensor, motion sensor, have you used it? This is not to say that these new technologies are used for use. Rather, we want to show that we already have new technologies. Don't waste them. It's time to change the previous web pages and the previous operating methods.
Using these features can make the user experience better. Some product managers or designers are still stuck in the HTML4 era in front-end knowledge. We need to share new knowledge with them.
The above are the main learning points summarized for you today, I hope I can help you!
If you want to work on the front-end and don’t know how to get started, you can comment on "Learning" in the message area. I will share my many years of experience with you, as well as some learning materials (like + forward)