Angular, react, polymer
I explain why angular can be so hot, it mainly solves the problem of which level? It solves the problem of rapid development. We know that there are many B/s products, its essence is still like C/s, just to do this in the browser, so some systems, it is unavoidable to write a large number of JS in the browser, and then use some kind of UI framework, it will be relatively large number of collaborative development, code will be a lot, In this type of system development process, from the cost point of view to solve two problems:
How to make the development process as fast as possible?
How to make the cost of change as small as possible?
The solution to these two problems is to be modular. The so-called component, in the traditional software domain may have some mature solution, but to get the web, especially the Web front-end this level, there is basically no general solution. The component does not just solve the problem of the "control" level, business data and logic also need to be made up to clarify their relationship, and angular "happen" to be very helpful in this respect, it separates UI and business logic cleanly, use dependency injection between modules to maintain relationships, easy to test, reusable , as an architect, it is easier to control the whole project.
We see a lot of people follow the angular, a large part does not grasp its essence, but is attracted by some corner advantage, so the use of the process of pain, if you can first recognize its essential advantages, and realize that it is really suitable for their own projects, will be able to be handy, both ways.
There are also some problems with the current angular version, which I have written two before and may be written in the near future. Angular officials are aware of these problems, they have planned the 2.0 version, this version of the idea is very good, interested people suggest you pay attention to, I will later on this incident a comment blog.
Now let's take a look at react.
Why many people are attracted by react, because he solves the problem of assembly from another level, which may be friendlier to the front end and can also parse templates on the server side. People who like react often use its virtual DOM, accurate updates to combat other frameworks, admittedly, it does very well in this area, but not high to the extent of the impact of the overall situation. What does that mean, it's a library that is primarily for DOM components, if used for a complete large product solution, or a lack of, its advantages focused on the top, but in fact, from a macro point of view, the efficiency of this layer is not so important, for example, you are a very sophisticated excavator, with a variety of sorting functions, But most of the time, it's rough digging, just like digging coal, and it doesn't matter how efficient you are in detail, but only in situations where you need precise control. Moreover, when the Web is RS out, the virtual Dom has a lot of problems to deal with, and the other frameworks can make the gap a lot smaller by improving the efficiency of data binding.
Although I said all is the flaw, but its realization way is really unique, is worth seeing.
Finally see polymer, it is based on the concept of Web RS, I would like to say something, but feel that their understanding of it is not profound, it is likely to mislead people. Let someone else say it.