Front-end framework and front-end class library

Misunderstanding of front-end framework

The value of a website lies in what value it can provide to users, what the website can do, and not in how it does it, therefore, when the website is still very small, it is worth the candle to pursue the website architecture framework. The same applies to front-end frameworks. For a simple page-based product, applications only rely on servers to generate Web pages and views, in addition, you only need to use some simple JavaScript or jquery to make the application more interactive, so a jquery front-end class library is enough, and there is really no need to use some tall frameworks.

Of course, the framework is indeed very useful, and the focus is to know when to use the framework. The experience and success model of large companies and large projects are of course important and worth learning from, but we cannot become blind. Only by deeply understanding the front-end framework and knowing when to use the Framework to solve the problems can we be targeted and hit the key.

 

Difference between front-end framework and front-end class library

Before using a framework, I think it is very important to find out the differences between a class library (such as jquery) and a framework (such as angularjs.

In short, the class library solves code or module-level multiplexing or complexity encapsulation problems. For example, it encapsulates a functional module that solves a complex problem into a function, provides a simple interface. Library is a tool that provides a lot of encapsulated methods. It doesn't depend on ourselves, that is, it doesn't affect our code structure.

The framework is more about the reuse of the pattern level and the specification of the program organization. The pattern here refers to MVC. In order to realize the decoupling of M and V, the complicated coupling relationship is transferred from the frequently changing business code to the infrequently changing framework for digestion. It provides a set of solutions for a single domain to improve development efficiency. If we choose to use a framework, we should follow the rules stipulated by the framework.

The main difference between the two is that jquery is centered on Dom operations, and the framework, which is precisely the MVC Framework, is centered on models, while Dom operations are appended. Therefore, the model-centric goal is to bring about a complete set of workflow changes, so that background engineers can compile the front-end model code to interconnect the background with the front-end, the interaction designer processes the interaction between the UI and the model. The UI Designer can focus on and process the HTML source code without barriers and submit them to the interaction engineer in the form of an Interface Template. This complete collaboration mechanism can greatly improve development efficiency. Use the MVC framework to better decouple front-end tasks.

Front-end framework and front-end class library