D
D
Deric2015-04-13 15:59:08
JavaScript
Deric, 2015-04-13 15:59:08

Promising JavaScript framework or why not AngularJS 1.x?

After the weekend, the question arose about the advisability of using Angular in the current project. It is very embarrassing that with the growth of the project we will stumble upon some "fundamental rake" of Angular, because of which the project is rewritten in the form of Angular 2.0. And it would seem that the project is far from complete, why not try Angular 2.0, start getting involved in ES6? However, the documentation for 2.0 is not enough, we are hard to learn, maybe there are alternatives?
So, you want to understand the direction of JS development? Which JS framework is the most promising in terms of both independent project and language development? What framework will allow the least painful "drive" into the server-side JS?
And I almost forgot: all this is considered for use in a local client application.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
M
Mikhail Osher, 2015-04-13
@miraage

What other fundamental rake? It's very interesting.
How many have not heard such words - at the output it turned out that people simply do not know how to solve problems within the framework of AngluarJS.

U
uvelichitel, 2015-04-13
@uvelichitel

What framework will allow the least painful "drive" into the server-side JS?
Meteor - www.meteor.com
Derby - derbyjs.com

I
Ilya Agarkov, 2015-04-23
@ElianL

ReactJS + Flux.
Here you can start to delve into server-side JS. since all this can be rendered both on the server and not on the client.
To the question "why not Angular 1.x"
There is something to scold or praise Angular for, so I think I will not consider its cons and shortcomings here.
But personally, I have already decided for myself that facebook is right and MVC is not the best solution for interfaces, and flux fits much better.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question