Why don't they like Ember.JS?

Question

JavaScript

I would like to know why they choose not Ember, but Angular / React / Backbone.
I worked on a fairly large Angular project for 5 months and developed a personal Ember project. The difference is significant in my opinion.

Answer 1

In my opinion, for two of the reasons: it has historically developed or it is so fashionable.
Somehow it turned out that Backbone, Angular, and not Ember are more popular in RuNet.
I think that in my vision of the reasons, I am more or less right, since very rarely anyone, when choosing a framework, conducts a full-fledged comparative study.
Usually, whoever Google has given more links to is taken as an ideal - after all, 86% cannot be wrong.

Answer 2

"Historically"
I think Angular quickly gained popularity because of, and I quote: "it was developed by Google." Well, then with a fairly large share of the "market", Angular keeps itself.
Actually a lot of things. which are not the best, but simply fashionable. For example, why use Git and not Mercurial? Why 1C, if there are better applications, but cheaper? etc.

Answer 3

1) Ember is (very) slow compared to other frameworks (judging by different tests)
2) Classes on classes drive classes (although it seems possible without them), when in others * put json and everything works
3) Observer model + set / get - gives its disadvantages and not everyone likes it

Answer 4

I met more than one article, the essence of which was that a person could not figure out why he didn’t enter the model correctly out of the RESTful api box, why use serializers at all, what is the difference and why split into initializer / instance-initializer, after which followed by the statement that in angular everything is simpler, there are fewer restrictions and you can do everything quickly (taking into account the fact that there are many examples of good admin panels on the network like Angulr, Metronic, etc.). Plus, not quite up-to-date documentation for the latest versions.
At one time, we started the project, and chose Ember for the front-end, which we do not regret at all. They switched from version 0.9.x to 1.13.x with minor problems, there will be no problems at all on 2.x.

Answer 5

According to Emebru, there is practically no relevant information in Russian, not everyone speaks English to the proper degree. They have clumsy tutorials, and yes, very active development, a lot of rapid changes.
Nevertheless, for myself, I chose Amber and slowly bite into it. Painfully close to me his philosophy. And in general, times are such that there are no options ...
And yes, the entry threshold is quite high, it is necessary to absorb a lot of contexts. However, I am convinced it is worth it.
PS: Angular did not take root for me - too much anarchy.
PS2: In 2016, I chose React.JS...

Answer 6

At the expense of love - dislike, it's all relative. I agree that the documentation in Russian on Amber is not enough. There are a couple of good resources, and the rest is scattered around the forums, etc. Yes, and the video in Russian is also counted on the fingers. 3 months ago, when choosing a framework for SPA (a fairly large resource, with a lot of real-time updates, APIs, etc.), I got stuck for a week. Too many of them all sorts of different things have been stuck lately. ) But for some reason, at the first glance at the structure and code of Ember, it immediately seemed familiar. The same story was with Laravel earlier. Yes, I spent a couple of weeks understanding his philosophy, but then everything went like clockwork. Almost all the functionality that I need in the project was implemented without any problems. In the English-speaking Internet, I found answers to 90% of the questions that arose. I got to the rest myself. Their API is now well documented. And judging by the result, I was not mistaken in choosing a framework. Benchmarks are also not always relevant. Since not everything depends on the tools, but also on the curvature or straightness of the hands.
In any case, until you try any tool, you will not understand whether it suits you or not. Who would not write anything.

Answer 7

I studied the specified framework for about a year. I dealt with MVC, templating, modularity, reactivity, working with CLI - in short, everything that appeared in the rest 2 years later.
At the moment - as the developers promised - new releases come out 2 times a month - and what else does a live framework need.
To refer to the lack of Russian-language documentation in general is somehow ridiculous. All code examples are there - why the Russian language.
Foreign videos generally stream under Mouzon, and even at a speed of 1.5-2x. Watch and pause when needed.
And so everything rests on orders, but no one bothers to start doing a new project on it.
The problem of supporting old codes and startups is also manifested in the comparison of react and view - very few people will rewrite the react code - only support it.