4 ms·

I lead an internal development team. We're constant building new apps and enhancing old ones. Ember has been a big win for us. Upgrading old apps is a breeze

I lead an internal development team. We're constant building new apps and enhancing old ones. Ember has been a big win for us. Upgrading old apps is a breeze. Every app has a consistent structure and the conventions make it easy for developers to move between projects. We don't need to worry about the individual pieces - routing, data, etc - we trust the core devs so that we only worry about business logic. We're experimenting with Ember Engines right now and I'm not sure how we'd replicate it if we were using React or Angular. All in all, I think it has made us incredibly productive. Outside of the code, the Ember team's communication skills are top notch. I feel like every time I tell my team that "XYZ is coming down the pipe", there's a clear plan of attack and any impact is minimal. In the last 3 years, I've never had to tell my boss that development will be paused to focus on a refactor/upgrade/maintenance. The biggest downside is in hiring, unfortunately. I don't look for Ember experience, but I have had to adjust my expectations when it comes to the learning curve.

vmware505 8y ago
Actually, learning Ember.js is quite easy nowadays. There are great free options, where you can go far in a few days: http://yoember.com http://yoember.com | https://guides.emberjs.com/v3.0.0/tutorial/ember-cli/ https://guides.emberjs.com/v3.0.0/tutorial/ember-cli/
- stocktech 8y ago
  Agreed, but experience has shown some kind of mental block in developers coming from other frameworks. ymmv
- msum 8y ago
  Also https://medium.com/ember-ish https://medium.com/ember-ish is incredibly useful.
Edwardzyc 8y ago
Are you guys hiring? (although I haven't used ember since..before 1.0)
jonesetc 8y ago
> Outside of the code, the Ember team's communication skills are top notch. I feel like every time I tell my team that "XYZ is coming down the pipe", there's a clear plan of attack and any impact is minimal. In the last 3 years, I've never had to tell my boss that development will be paused to focus on a refactor/upgrade/maintenance. Really? We had the exact opposite experience with major upcoming refactors that were poorly handled. Deprecating controllers, adding routable controllers, multiple changes in the rendering systems (handlebars, htmlbars, glimmer), and lots of confusion around coordinating release of core, data, and cli. Enjoyed most things outside of that though. Learning curve early on was rough, but now it seems a lot better and looks they are rallying back up for good improvements after the 3.0 release.
- stocktech 8y ago
  Maybe it's because we're slower on the release cycle? We stick to LTS and a little extra depending on our workload. We also committed to using controllers thinking it would be easy to convert to routable components later on, when the routable components never landed it made our lives easier. Otherwise, I haven't paid attention to the core,data, and cli release schedules.
- gavinjoyce 8y ago
  1.x to 2.0 was a little rough, but so much better than the "all apps left behind" approach of Angular 1.x to 2.0. Ember's 2.x to 3.0 upgrade path was much improved as earlier mistakes were learned from. Trajectory matters, and Ember had got a really great trajectory for apps that value longevity now.

vmware505 8y ago

Actually, learning Ember.js is quite easy nowadays. There are great free options, where you can go far in a few days: http://yoember.com http://yoember.com | https://guides.emberjs.com/v3.0.0/tutorial/ember-cli/ https://guides.emberjs.com/v3.0.0/tutorial/ember-cli/

stocktech 8y ago
Agreed, but experience has shown some kind of mental block in developers coming from other frameworks. ymmv
msum 8y ago
Also https://medium.com/ember-ish https://medium.com/ember-ish is incredibly useful.

Edwardzyc 8y ago

Are you guys hiring? (although I haven't used ember since..before 1.0)

jonesetc 8y ago

> Outside of the code, the Ember team's communication skills are top notch. I feel like every time I tell my team that "XYZ is coming down the pipe", there's a clear plan of attack and any impact is minimal. In the last 3 years, I've never had to tell my boss that development will be paused to focus on a refactor/upgrade/maintenance. Really? We had the exact opposite experience with major upcoming refactors that were poorly handled. Deprecating controllers, adding routable controllers, multiple changes in the rendering systems (handlebars, htmlbars, glimmer), and lots of confusion around coordinating release of core, data, and cli. Enjoyed most things outside of that though. Learning curve early on was rough, but now it seems a lot better and looks they are rallying back up for good improvements after the 3.0 release.

stocktech 8y ago
Maybe it's because we're slower on the release cycle? We stick to LTS and a little extra depending on our workload. We also committed to using controllers thinking it would be easy to convert to routable components later on, when the routable components never landed it made our lives easier. Otherwise, I haven't paid attention to the core,data, and cli release schedules.
gavinjoyce 8y ago
1.x to 2.0 was a little rough, but so much better than the "all apps left behind" approach of Angular 1.x to 2.0. Ember's 2.x to 3.0 upgrade path was much improved as earlier mistakes were learned from. Trajectory matters, and Ember had got a really great trajectory for apps that value longevity now.