In this article, reference to https://www.oschina.net/question/2680454_2199260#tags_nav\
Review the front-end trends
Table layouts and inline styles are everywhere
At the beginning of the Web front end, all use table for layout, there are a lot of inline style, with the popularity of DIV+CSS layout, table layout was eliminated. For now, tables are just for displaying data.
Jquery rules the world
With the popularity of jquery, compatibility is no longer the main problem plaguing front-end development. Then the jquery ecosystem began to evolve, and jquery and jquery plug-ins took over web front-end development.
HTML 5 and CSS 3
With the release and implementation of HTML5 and CSS3 standards, it seems that the front-end development saw the dawn of front-end unification, leading the front-end into a wave of learning H5 climax, this time random interview, will ask you will H5, in fact, their website does not use H5.
MV** Frame revolution
With the update of the browser, IE was gradually eliminated, compatibility is no longer a problem, the big god is not only satisfied with the operation of DOM, and then in the operation of DOM and encapsulation, resulting in a variety of MV, MVVM… Frames are catching on.
Front-end componentization is popular
React’s emergence greatly promoted the development of front-end componentization, and various React components mushroomed. At this point, the previous front-end code is still available, such as the jquery plugin can be used in React, but it is very painful to use, React is not recommended.
Big front end?
The emergence of React-Native allows the front end to call Native components without knowing the implementation of Android and iOS Native components. Then Ali WEEX also open source, said WEEX is A framework for building Mobile cross-platform UI. And then, this little app of wechat. The principle and implementation are similar, but the key is that one set of code cannot be compatible in three ecosystems, each with its own rules of the game. Feel with the development of the front end, it is estimated that a slightly larger factory will do their own front end ecology, in accordance with their own rules to make a similar WEEX or wechat application number of things out, let others to use after. Doesn’t this feel like a dead beat? NO ZUO NO DIE,NO TRY NO HIGH!
Personal feelings
At the beginning, I chose to work on the front end, because the front end is simple, what you see is what you get, and a jquery plug-in can do everything.
And now? No longer! The advent of ES6 also complicates the previously simple JS. React has turned the express train of componentization on its head, but internal state management has also become complex, resulting in Flux, ReFlux, Redux, Mobx and other state-management frameworks (Mobx officially claims not to be a React state-management framework, just a state-management approach).
To shortly before a little step on the hole WEEX, also found that the front to learn a lot of things, and then found that step on the pit, abandoned. Now this micro channel small application, it is estimated that the front end has to step on a lot of pits. The terrible thing is to build so many wheels and not know what will happen to them.
WEEX just came out anyway. It’s fine. Now what? Lukewarm! Do not know as micro letter old rival, pay treasure can also make a pay treasure application number, and then use WEEx to develop? It feels like the new technology on the front end is all about knocking down old ideas and starting all over again. Finally, or bitter silently write code of the front dog.
Front-end, it’s not easy to say I love you. \
conclusion
To paraphrase Charles Dickens: it is the best of times, it is the worst of times.
The opinion in this article is purely personal, if there is any mistake, please correct, if you do not agree, please spray. I think above, this elder brother write good