I did a project with NG 1.5 and found it to be a huge pit. Basically, it should be the best practice to use it according to the framework of JHipster. Resolve is used to load data in advance before routing, reduce the scope of variables and other details. . .
First of all, the mode of this thing is still very anti-web, especially in WeChat, because the cache of WeChat is very serious, and the speed of NG is obviously related to the preloading of a large number of pages, which makes debugging more difficult; moreover, due to the authorization in WeChat , especially when multiple systems authorize each other, there are many jumps, so paths such as #xxx are inconsistent with the request path of the request, resulting in a large number of js-side redirects to request authorization, and it cannot be processed directly on the server side by Filter at one time complete.
I recently researched JD.com's Wechat website and found that it is all a one-to-one agile model, and there is no such method as NG.
Moreover, the NG mode does not bring too much convenience to server-side development. The only commendable thing is that API interaction is simplified in some places, and H5 and APP can call a set of APIs in a unified manner.
However, there are still more problems with this thing than benefits. It is more like a framework that is easy to use in some specific occasions, or a framework that front-end programmers change for the sake of change; and this affects my view of vue: Is it right? the same pit?
At present, I will continue to pay attention to these two frameworks and see if there are any killer apps in the future.