3 ms·

Really Sad to me that Ember.js gets so little love. It is hands above Angular 1 or 2 in my mind and the only JS front end framework that I feel productive in.

by anm89 10y ago

petercooper 10y ago
I run a JavaScript focused Twitter account with 235K followers and on analyzing our 2016 stats this week, we found most of the Ember things we linked ended up in the bottom quarter of tweets ranked by engagement :-( I know Ember, know the (great) people involved, and try to promote it when I can, but for some reason my audiences aren't keen on it in large numbers. Yet whenever I do encounter an Ember user, they are always so full of praise, and ThoughtWorks gave it a strong recommendation recently too.
ajmurmann 10y ago
It seems like user satisfaction for Ember is lagging behind anything but Angular 1 and Backbone. Presumably Angular 1 and Backbone don't get repeat customers because Angular 2 is out now and Backbone is pretty old. Source: http://stateofjs.com/2016/frontend/ http://stateofjs.com/2016/frontend/
ArtDev 10y ago
Probably because everyone knows what it is. No use to "star" it.
urukhaifive 10y ago
This is anecdotal, but I believe this is due to the steep learning curve of ember.js. As someone who is just trying to pick up this framework, I feel like a complete outsider who is left to fumble around for months until it "clicks" and only then can I understand what is actually going on. I have been playing with it for the past 4 weeks, and I still feel more in the dark than I did after about a week of React JS/redux. The tutorial in the ember guides has you use mirage, a client-side mock-server, which is great for learning how to use ember.js in a vacuum. You are completely on your own in figuring out to serve it real data. Also, if you want to follow ember.js recommended conventions you need to learn how to serialize/deserialize your API into the JSON API specification. Something that is proving to be a pain in the ass when trying to work with rails strong parameters. It is causing me to relearn basic CRUD operations. Most of my time learning ember has been spent rummaging through GitHub issues for active model serializers or jsonapi resources. Everyone in the ember community swears by the "Data down, Actions Up" philosophy, and yet it isn't mentioned or explained anywhere in their documentation. As someone who is brand new to the community, how am I supposed to understand the proper way of doing things? Should I be creating actions in my routes, controllers, or components? Do I even need to use controllers since the apparent trend is moving toward components? Is ember-data capable of requesting data from the API based on the relationships I build within ember models? I was able to install a single gem, serve standard rails JSON, and I was up and running with reactjs/redux. Maybe I will be more productive in ember.js with the loveliness that is ember-cli, but learning ember.js is a much more expensive initial investment in my opinion.

Really Sad to me that Ember.js gets so little love. It is hands above Angular 1 or 2 in my mind and the only JS front end framework that I feel productive in.

by anm89 10y ago

Really Sad to me that Ember.js gets so little love. It is hands above Angular 1 or 2 in my mind and the only JS front end framework that I feel productive in.

petercooper 10y ago

I run a JavaScript focused Twitter account with 235K followers and on analyzing our 2016 stats this week, we found most of the Ember things we linked ended up in the bottom quarter of tweets ranked by engagement :-( I know Ember, know the (great) people involved, and try to promote it when I can, but for some reason my audiences aren't keen on it in large numbers. Yet whenever I do encounter an Ember user, they are always so full of praise, and ThoughtWorks gave it a strong recommendation recently too.

ajmurmann 10y ago

It seems like user satisfaction for Ember is lagging behind anything but Angular 1 and Backbone. Presumably Angular 1 and Backbone don't get repeat customers because Angular 2 is out now and Backbone is pretty old. Source: http://stateofjs.com/2016/frontend/ http://stateofjs.com/2016/frontend/

ArtDev 10y ago

Probably because everyone knows what it is. No use to "star" it.

urukhaifive 10y ago

This is anecdotal, but I believe this is due to the steep learning curve of ember.js. As someone who is just trying to pick up this framework, I feel like a complete outsider who is left to fumble around for months until it "clicks" and only then can I understand what is actually going on. I have been playing with it for the past 4 weeks, and I still feel more in the dark than I did after about a week of React JS/redux. The tutorial in the ember guides has you use mirage, a client-side mock-server, which is great for learning how to use ember.js in a vacuum. You are completely on your own in figuring out to serve it real data. Also, if you want to follow ember.js recommended conventions you need to learn how to serialize/deserialize your API into the JSON API specification. Something that is proving to be a pain in the ass when trying to work with rails strong parameters. It is causing me to relearn basic CRUD operations. Most of my time learning ember has been spent rummaging through GitHub issues for active model serializers or jsonapi resources. Everyone in the ember community swears by the "Data down, Actions Up" philosophy, and yet it isn't mentioned or explained anywhere in their documentation. As someone who is brand new to the community, how am I supposed to understand the proper way of doing things? Should I be creating actions in my routes, controllers, or components? Do I even need to use controllers since the apparent trend is moving toward components? Is ember-data capable of requesting data from the API based on the relationships I build within ember models? I was able to install a single gem, serve standard rails JSON, and I was up and running with reactjs/redux. Maybe I will be more productive in ember.js with the loveliness that is ember-cli, but learning ember.js is a much more expensive initial investment in my opinion.