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
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
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
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
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
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
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
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
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
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
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
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
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
balint
trishagee
hogelog
linyows
4su_para
kaminashi
eijikominami
shigashiyama
lycorp_recruit_jp
kazushi_ohata
niwatakeru
miu_crescent
shonansurvivors
danielanewman
tanoku
thoeni
aki_iinuma
samanthasiow
sonatard
palkan
mojombo
eileencodes
tammyeverts
philhawksworth
holman
