3 ms·
> 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
by 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 agoMaybe 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 ago1.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.