Home  >  Article  >  Web Front-end  >  Outlook for the future of the front-end

Outlook for the future of the front-end

零下一度
零下一度Original
2017-06-26 13:38:331876browse

 1. User demand is increasing day by day.

Your stage is very big. As a "craft", front-end requires everyone to create more complex pages faster.

 2. New Javascript features.

Jquery has brought us a lot of happiness, but too many direct DOM operations and chaotic data management have led to low performance, so it is almost time to say goodbye to it. Various new front-end frameworks such as React and Vue focus more on DOM optimization and state management, and can cope with more complex needs.

Typescript seems to be the long-term winner because it has a greater degree of freedom and is more friendly to develop than js.

 3. We don’t make pages, we make systems.

Style manuals, system design, and pattern libraries are becoming more and more important in development. We no longer code out pages one by one, but design a system based on needs. We have to admire the development ability of js.

4. The boundaries between native and web are gradually blurring.

Gradually, the web can do things that native apps can do, such as audio, video and online payment. What everyone really cares about is whether the application works well, not how it is built. The web will be a huge stage for PC applications or mobile phone applications.

 5.URLs are the highlight of the future.

In the vast ocean of the Internet, you can dig out what you need through URL. It has to be said that URL is one of the most important inventions in human history. URLs will be the future marketing arena.

 6. Performance plays an important role.

Human beings can no longer tolerate slowly loading web pages. They must either respond instantly or shut down.

7. CSS should also be more modular.

You may not believe it, but CSS also has a saying of "memory leak", so in the future, its scope will be narrowed and bound to components.

8. CSS preprocessing gradually fades out of the stage.

The CSS preprocessor helped us save a lot of energy. In the end, we implemented CSS modularization, in a sense, through the preprocessor. When hybrid CSS writing takes off, today's CSS preprocessing methods can be retired.

9. Writing HTML and CSS well is still important.

The way structures and styles are composed and parsed under browsers are constantly changing with the development of technology. But you still need to know what kind of HTML structure is beneficial to SEO and easier to read, and what kind of CSS is obviously more scientific.

 10. Engineering processing can make the page more competitive.

Various packaging and processing tools can greatly improve page performance, such as what code is presented to the browser, when, where and how components are presented, and unused code is temporarily thrown away, etc. The web stage is evolving, and engineering tools will certainly not lag behind.

Wonderful comments and questions for everyone to think about:

ernest: You said that the "page" will disappear, But you also said that we rely on URLs to find specific information. So the page disappears, where do we jump to by using URLs?

Phil Nelson: This concept of "system" will hurt many projects and people. Toys (frameworks) are fun, but you have to be realistic.

Goose: I don’t agree with your point about jquery. There is data to prove it. There is no doubt that its market share will decline, but its status remains irreplaceable.

(I won’t post all the discussions and quarrels one by one. Everyone should think carefully like them when reading the article, and don’t question the big guys when you see them^_^)

The above is the detailed content of Outlook for the future of the front-end. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn