3 ms·

I still dont understand this fatigue rant around JavaScript. Because I started to work with Ember.js 4 years ago, and it is the solution for everything. The fra

I still dont understand this fatigue rant around JavaScript. Because I started to work with Ember.js 4 years ago, and it is the solution for everything. The framework evolved nicely and works perfectly. It was not a bet, it was serious choice which based on a real perspective and concept. Ember is matured and production ready for years now. You can focus on your product. So, as an Emberjs dev never felt that problem than other js developers. Dont experiment, start using the best tool out on the market... no more crying only happiness. ;)

seanwilson 11y ago
> I still dont understand this fatigue rant around JavaScript. Because I started to work with Ember.js 4 years ago, and it is the solution for everything. The framework evolved nicely and works perfectly. It was not a bet, it was serious choice which based on a real perspective and concept. Yup, it doesn't make sense to keep chasing the perfect solution. Developers wouldn't be suffering from fatigue if they focused on "done is better than perfect".
- BWStearns 11y ago
  Sure, if you're always in a position to pick your stack then just sticking with your proven tech works. If you're working for other people with existing code you might need to learn a whole new JS stack every time you switch employers. Since you're already engaged in a Sisyphean cycle of learning new ways to JS why not be on the lookout for perfect for when you do get to pick your own?
fokinsean 11y ago
Yeah, Ember is awesome. Hassle free tooling and you can get up and going in minutes.
anonyfox 11y ago
Ember even has a LTS version now!
mpk 11y ago
Ember is fantastic, the oldest projects I have are about 4 years old and have been (more-or-less) painlessly upgraded every now and again. Everything is ember-cli and ember-cli-deploy now. Time and time again it shows that Ember is a community project that has a strong focus on scalability and maintainability over time. I also do a lot of work in Angular and React (this year) and all the tooling, build, best practices change every couple of months. A lot of people complain about Ember's learning curve, but the things you learn _stay relevant_. Personally I'd rather invest in that kind of knowledge than learning yet another arbitrary build system.
rk06 11y ago
to me, ember is the only source of peace in js framework wars. I do not use it yet.(cause i am js noob). but if i require a full blown js framework, ember will be my choice.
- vmware513 11y ago
  You can learn it quickly from this free tutorial: http://yoember.com http://yoember.com
zeemonkee3 11y ago
Right now I know of a company that needs to overhaul their front end. They don't have a lot of available developer resources and their core strength is backend (Python/Django). I'm sorely tempted to recommend Ember. Angular is in transition and the whole React circus would be overwhelming for them. Ember fits in very well with the Django philosophy and there are plugins to make them play nicely. Ember has a learning curve but it looks like it would pay off long-term.
dwaltrip 11y ago
Ember is nice, but it is a gigantic framework with a steep learning curve, and very heavy on the wire (lots of kb). I used it at my last job. I'm using mithril.js right now for a side project, with basic ES5 and no build tools. Mithril has a tiny API but still offers surprising amounts of power. I'm enjoying the simplicity of everything. It's been nice spending way less cognitive energy to understand how all the pieces fit together =) I may have to add some tooling in when I deploy the finished project, but I'm going to keep it as minimal as possible.
marknutter 11y ago
For people who have used more batteries-included style frameworks like Ember, the churn isn't as bad. But for those who tend to lean more toward small libraries like Backbone and React, the churn can be overwhelming.

seanwilson 11y ago

> I still dont understand this fatigue rant around JavaScript. Because I started to work with Ember.js 4 years ago, and it is the solution for everything. The framework evolved nicely and works perfectly. It was not a bet, it was serious choice which based on a real perspective and concept. Yup, it doesn't make sense to keep chasing the perfect solution. Developers wouldn't be suffering from fatigue if they focused on "done is better than perfect".

BWStearns 11y ago
Sure, if you're always in a position to pick your stack then just sticking with your proven tech works. If you're working for other people with existing code you might need to learn a whole new JS stack every time you switch employers. Since you're already engaged in a Sisyphean cycle of learning new ways to JS why not be on the lookout for perfect for when you do get to pick your own?

fokinsean 11y ago

Yeah, Ember is awesome. Hassle free tooling and you can get up and going in minutes.

anonyfox 11y ago

Ember even has a LTS version now!

mpk 11y ago

Ember is fantastic, the oldest projects I have are about 4 years old and have been (more-or-less) painlessly upgraded every now and again. Everything is ember-cli and ember-cli-deploy now. Time and time again it shows that Ember is a community project that has a strong focus on scalability and maintainability over time. I also do a lot of work in Angular and React (this year) and all the tooling, build, best practices change every couple of months. A lot of people complain about Ember's learning curve, but the things you learn _stay relevant_. Personally I'd rather invest in that kind of knowledge than learning yet another arbitrary build system.

rk06 11y ago

to me, ember is the only source of peace in js framework wars. I do not use it yet.(cause i am js noob). but if i require a full blown js framework, ember will be my choice.

vmware513 11y ago
You can learn it quickly from this free tutorial: http://yoember.com http://yoember.com

zeemonkee3 11y ago

Right now I know of a company that needs to overhaul their front end. They don't have a lot of available developer resources and their core strength is backend (Python/Django). I'm sorely tempted to recommend Ember. Angular is in transition and the whole React circus would be overwhelming for them. Ember fits in very well with the Django philosophy and there are plugins to make them play nicely. Ember has a learning curve but it looks like it would pay off long-term.

dwaltrip 11y ago

Ember is nice, but it is a gigantic framework with a steep learning curve, and very heavy on the wire (lots of kb). I used it at my last job. I'm using mithril.js right now for a side project, with basic ES5 and no build tools. Mithril has a tiny API but still offers surprising amounts of power. I'm enjoying the simplicity of everything. It's been nice spending way less cognitive energy to understand how all the pieces fit together =) I may have to add some tooling in when I deploy the finished project, but I'm going to keep it as minimal as possible.

marknutter 11y ago

For people who have used more batteries-included style frameworks like Ember, the churn isn't as bad. But for those who tend to lean more toward small libraries like Backbone and React, the churn can be overwhelming.