I am Teambition front-end, React.js community manager, and have related interests.
Backbone is a framework that came out in the early years, and the solution is clear. The disadvantage is that there are too many View layers, which will make large projects difficult.
In addition, the Model design is tightly bound to Ajax, which I don’t quite understand. It may work in certain scenarios.
React.js is dedicated to the View layer, at least I think it is the best framework for the View part currently,
Performance, big company backing, ease of use, community, Chinese tutorials, everything is well-established.
The disadvantage is that the data layer solution is immature, and it will need to be able to withstand Facebook's enlargement strategy later.
Angular is a framework that I am not familiar with. Although I have read many articles, I have not studied it in depth.
Considering that Google is making major changes to 2.0, and Google is officially launching Polymer, I am not optimistic about it.
I heard from experts in the community that students with a Java background can learn it very easily... Try it yourself.
If you consider server-side rendering for mobile pages, React is more suitable for front-end and back-end shared code.
But there is a cost, it’s just that Backbone and Angular cost more.
You can spend a few hours trying react, http://www.hubwiz.com/course/552762019964049d1872fc88/;
Then spend a few hours trying angularjs, http://www.hubwiz.com/course/547c3e3b88dba0087c55b4e5/
As well as angularjs and ionic, http://www.hubwiz.com/course/55010505e564e5172c0b9405/
To make a simple comparison, it is better to try before choosing.
Since I use Angular myself, I recommend it. I use Angular for web and ionic for mobile. The communities of these technologies are very active, so I won’t comment on others~ Just sauce.
Angular is a heavy-duty framework produced by Google. The characteristic of a heavy-duty framework is the development of fast code and high versatility. However, the design of angular is intrusive, which means that you need to learn many features that Google imposes on HTML5. Personally, I think this idea itself is a Wrong, Google seems very arrogant in this regard, angular2 doesn’t know how many more people it will harm.
Backbone is a lightweight framework with features that are almost the opposite of Angular. It is completely non-intrusive, compact, and highly scalable. However, the disadvantage is that development is slow and many "wheels" need to be built by yourself. Another disadvantage is that the code has low versatility and is difficult to reuse, and the team needs to set up Standardization can reduce maintenance costs. If you want backbone to take off, you need a lot of code accumulation and good code specification support. Personally, I prefer backbone
I haven’t had time to study React yet, but after reading a lot of reviews, it seems that the development efficiency is relatively high and the ideas are relatively advanced.
React is an interface library, you can explore your own best practices in your own way. The officially recommended model is Flux (I tried it, and the final result was similar to Flux).
The rest all come with their own best practices. Angular is TDD, which Backbone doesn’t understand. Ember is MVC plus JSONAPI.
If you like to explore React, you can’t go wrong with it, and it’s easy to learn. You can write decent things after learning less than ten functions.
The previous apps didn’t use frameworks. I wrote my own logic and template rendering, and there was nothing difficult about it! I guess the project is not very complicated!
I am Teambition front-end, React.js community manager, and have related interests.
Backbone is a framework that came out in the early years, and the solution is clear. The disadvantage is that there are too many View layers, which will make large projects difficult.
In addition, the Model design is tightly bound to Ajax, which I don’t quite understand. It may work in certain scenarios.
React.js is dedicated to the View layer, at least I think it is the best framework for the View part currently,
Performance, big company backing, ease of use, community, Chinese tutorials, everything is well-established.
The disadvantage is that the data layer solution is immature, and it will need to be able to withstand Facebook's enlargement strategy later.
Angular is a framework that I am not familiar with. Although I have read many articles, I have not studied it in depth.
Considering that Google is making major changes to 2.0, and Google is officially launching Polymer, I am not optimistic about it.
I heard from experts in the community that students with a Java background can learn it very easily... Try it yourself.
If you consider server-side rendering for mobile pages, React is more suitable for front-end and back-end shared code.
But there is a cost, it’s just that Backbone and Angular cost more.
You can spend a few hours trying react, http://www.hubwiz.com/course/552762019964049d1872fc88/;
Then spend a few hours trying angularjs, http://www.hubwiz.com/course/547c3e3b88dba0087c55b4e5/
As well as angularjs and ionic, http://www.hubwiz.com/course/55010505e564e5172c0b9405/
To make a simple comparison, it is better to try before choosing.
Since I use Angular myself, I recommend it. I use Angular for web and ionic for mobile. The communities of these technologies are very active, so I won’t comment on others~ Just sauce.
Angular is a heavy-duty framework produced by Google. The characteristic of a heavy-duty framework is the development of fast code and high versatility. However, the design of angular is intrusive, which means that you need to learn many features that Google imposes on HTML5. Personally, I think this idea itself is a Wrong, Google seems very arrogant in this regard, angular2 doesn’t know how many more people it will harm.
Backbone is a lightweight framework with features that are almost the opposite of Angular. It is completely non-intrusive, compact, and highly scalable. However, the disadvantage is that development is slow and many "wheels" need to be built by yourself. Another disadvantage is that the code has low versatility and is difficult to reuse, and the team needs to set up Standardization can reduce maintenance costs. If you want backbone to take off, you need a lot of code accumulation and good code specification support. Personally, I prefer backbone
I haven’t had time to study React yet, but after reading a lot of reviews, it seems that the development efficiency is relatively high and the ideas are relatively advanced.
React is an interface library, you can explore your own best practices in your own way. The officially recommended model is Flux (I tried it, and the final result was similar to Flux).
The rest all come with their own best practices. Angular is TDD, which Backbone doesn’t understand. Ember is MVC plus JSONAPI.
If you like to explore React, you can’t go wrong with it, and it’s easy to learn. You can write decent things after learning less than ten functions.
angluar writes quickly,
Backbone can be used with reactjs
Learn reactjs well and you can play reactnative
The previous apps didn’t use frameworks. I wrote my own logic and template rendering, and there was nothing difficult about it! I guess the project is not very complicated!
Strictly speaking, react is just the V layer in MVC, which is usually used with Flux.
backbone + zepto should be able to meet your needs for writing webapps
http://www.hubwiz.com/course/54f3ba65e564e50cfccbad4b/