First, slash and burn (Static page-based, also known as Web 1.0)
The interface is mainly composed of HTML, a small amount of javascript, mainly used for form verification and so on. Page by JSP, ASP, front and back responsibility is not clear, or there is no front end
The front-end view code, together with the Java or. NET code of the business logic, is not easy to maintain.
At this stage, a component bud begins to emerge.
Ii. Bronze Age (back-end MVC)
In order to reduce the complexity, the backend is the starting point, with the Web Server layer of the schema upgrade.
Structs, SPRINGMVC, Freemarker
The beginning and end of the work division began to become clear
Third, Iron Age (Ajax)
2004 Gmail like the wind of the woman came to the world, and soon 2005 Ajax formally put forward, plus the CDN began to use a lot of static resource storage, so there is a JavaScript king return of the SPA (single page application application) era
The front and back end of the division is very clear, the front and back of the key collaboration point is the Ajax interface
In this period, with the emergence of good user experience products, front-end development more and more complex, the Web front-end class library grew rapidly
Existing challenges: front-end interface conventions, the increase of front-end code, and the problem of code organization at the beginning of development
Iv. Industrial Revolution (front-end MVC)
Front-end development is booming, starting to consider: How to better modular development, how business data is organized, and how interfaces and business data interact with each other;
There are some front-end MVC, MVP, MVVM frameworks that we collectively refer to as the mv* framework
The emergence of some modular development architecture, Require.js, Sea.js
The front and back responsibilities are clear. The front end works on the browser side, and the backend works on the server side. It is very good to realize the parallel development of front-end separation.
Full async, bad for SEO. The service side is often required to do the simultaneous rendering of the downgrade scheme.
Performance is not optimal, especially in the mobile Internet environment.
Five, the full stack era (node. js)
In the trial phase, with the rise of node. JS, JavaScript began to be able to run on the server. Front-end developers are responsible for two UI tiers.
As far as I know, at home, large internet companies are now basically able to reach the fourth stage, most IT companies are still in the second and third stages, and a few are still in the slash-and-burn phase, mainly to maintain some legacy systems or to do some work based on legacy systems.
What stage does your company belong to? If you're a front-end, what stage are you in?
At what stage is your company's front-end level? Go