Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Why you should consider Ember.js for your next project

Balint Erdi
January 20, 2017

Why you should consider Ember.js for your next project

My talk given at AgentConf 17, in Dornbirn Austria, on January 20th, 2017.

Balint Erdi

January 20, 2017
Tweet

More Decks by Balint Erdi

Other Decks in Technology

Transcript

  1. My Ember.js story • January 2013 • Once I grokked

    it, I loved it • Became an Ember.js consultant and writer • Made a screencast series, wrote dozens of blog posts, held workshops, presented at conferences • Wrote a book for beginners • Still going strong
  2. Why Ember? 1. The power of conventions 2. Batteries included

    3. Incredible tooling 4. Testing 5. Backward compatibility as a tenet 6. Rich ecosystem of add-ons 7. Documentation 8. Reliable, regular release cycle 9. MIT license 10. Public RFC process
  3. “It’s no secret that it has a steeper learning curve

    compared to some other frameworks but once you’ve got over that, it makes you a really productive developer with its conventions and opinions acting as useful guard rails. Features get delivered to the market quicker.” Why we love Ember at British Gas – British Gas
  4. “Entrusting high-level architectural technology decisions to engineers who have limited

    experience in a domain often leads to bikeshedding and bad decisions —  and this showed in the side project we did.” Choosing Ember over React in 2016 – Instant 2FA
  5. “We had a smooth transition to the 2.x series when

    it came about as the transition path was well communicated in advance and there were addons that helped with the transition.” Why we love Ember at British Gas – British Gas
  6. “They know that a team paralyzed with doubt about whether

    they’re coding using modern techniques won’t be able to focus on writing the best apps they can today. And this is why changes to the framework are always accompanied by an upgrade path for older apps.” Safety of the herd - Ryan Toronto
  7. The addon eco-system is massive and the emberaddons website along

    with its ember observer score makes it easy to find the right one for your needs. Why we love Ember at British Gas – British Gas
  8. “The cost of learning & training never disappears, but the

    key trick here is broadly sharing the cost. Each time you force developers to make a curation decision with multiple valid answers, you fragment the pool of people who can share this cost. (…) That is why I'm so happy with the massive level of investment the Ember community pours into shared solutions. Shared solutions are harder to create than one-offs, but they're incredibly valuable.” Strong Conventions Make Hiring Easier – Edward Faulkner
  9. “Software gives us the power to embed skills and knowledge

    into tools. Doing this is hard work and it takes time to iteratively improve. But there's an immense payoff when you put world-class, best- practice knowledge into the hands of every person who has something they want to create.” Lake Wobegon Web Development – Edward Faulkner
  10. “The result is a culture of "many tiny libraries" that

    gets the tradeoff backwards: by overemphasizing the implementation simplicity of each library, there is an explosion of total interface complexity for the programmer -- once you integrate a sufficient number of tiny libraries to deliver ambitious capabilities.” On Interface Complexity vs Implementation Complexity – Edward Faulkner
  11. “When people reject the idea of ambitious, powerful abstractions in

    favor of "a diverse ecosystem...[of] small, focused, simple and robust libraries" they are confusing implementation with interface. Yes, the implementation of a powerful abstraction should be separated into focused and robust libraries. But if its interface exposes all of those libraries, it will be a poor interface for getting things done.” On the irony of programmers who don’t like abstractions – Edward Faulkner
  12. “On the contrary: the complexity of the RFC shows that

    this is a problem complex enough to justify having one well-thought-out community solution. It's not the easy stuff that needs to be standardized, it's the hard stuff.” Edward Faulkner commenting on the Module Unification RFC
  13. “The whole point of Ember is to identify that kind

    of problem and solve it together. Even though general solutions are harder to find than one-off "it works for me" solutions, it is massively more valuable in the long run.” Edward Faulkner commenting on the Module Unification RFC
  14. “The whole point of Ember is to identify that kind

    of problem and solve it together. Even though general solutions are harder to find than one-off "it works for me" solutions, it is massively more valuable in the long run.” Edward Faulkner commenting on the Module Unification RFC