Slide 1

Slide 1 text

Why you should consider Ember.js for your next project Agent Conference, Dornbirn, 01/20/2017

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

Interrail?

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

Balint Erdi balinterdi baaz on Twitter https://balinterdi.com

Slide 8

Slide 8 text

https://balinterdi.com/agentconf17

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

A framework for creating ambitious web applications

Slide 12

Slide 12 text

A framework for creating ambitious web applications cozy

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

An open source SDK for the web

Slide 15

Slide 15 text

Ember in 5 minutes

Slide 16

Slide 16 text

Route Controller Template Component Model instantiates renders serves as context for instantiates Helper uses uses

Slide 17

Slide 17 text

/bands/1/songs

Slide 18

Slide 18 text

/bands/1/songs

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

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

Slide 21

Slide 21 text

1. The power of conventions

Slide 22

Slide 22 text

“Make decisions so your users don't have to.”

Slide 23

Slide 23 text

Less time to get up & running on new projects

Slide 24

Slide 24 text

Lower maintenance, hiring and consulting costs

Slide 25

Slide 25 text

More team flexibility

Slide 26

Slide 26 text

“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

Slide 27

Slide 27 text

2. Batteries included

Slide 28

Slide 28 text

Everything just works

Slide 29

Slide 29 text

More time to concentrate on what matters

Slide 30

Slide 30 text

Less bikeshedding

Slide 31

Slide 31 text

The aggregate wisdom and consideration of several people & several years

Slide 32

Slide 32 text

“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

Slide 33

Slide 33 text

3. Incredible tooling

Slide 34

Slide 34 text

Ember CLI

Slide 35

Slide 35 text

$ ember new agent-conf

Slide 36

Slide 36 text

ES2015 and ES2016 via Babel

Slide 37

Slide 37 text

Generators

Slide 38

Slide 38 text

$ ember g route cities

Slide 39

Slide 39 text

$ ember g component city-selector

Slide 40

Slide 40 text

Live reload

Slide 41

Slide 41 text

Ember Inspector

Slide 42

Slide 42 text

No content

Slide 43

Slide 43 text

4. Testing

Slide 44

Slide 44 text

$ ember g component-test city-selector

Slide 45

Slide 45 text

$ ember g acceptance-test bands

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

$ ember test --server

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

On CI servers, run `ember test`

Slide 50

Slide 50 text

5. Backward compatibility as a tenet

Slide 51

Slide 51 text

“No app left behind”

Slide 52

Slide 52 text

Most things should keep working without anyone noticing

Slide 53

Slide 53 text

“Stability without stagnation”

Slide 54

Slide 54 text

Clear communication about deprecations

Slide 55

Slide 55 text

“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

Slide 56

Slide 56 text

A bridge to the future

Slide 57

Slide 57 text

“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

Slide 58

Slide 58 text

Goodies for free

Slide 59

Slide 59 text

HTMLBars rewrite (Ember 1.10 - 2015/02)

Slide 60

Slide 60 text

Glimmer 1 rewrite (Ember 1.13 - 2015/06)

Slide 61

Slide 61 text

Glimmer 2 rewrite (Ember 2.10 - 2016/11)

Slide 62

Slide 62 text

Kind of like the JVM

Slide 63

Slide 63 text

No content

Slide 64

Slide 64 text

6. Rich ecosystem of add-ons

Slide 65

Slide 65 text

No content

Slide 66

Slide 66 text

The world is an “ember install” away

Slide 67

Slide 67 text

$ ember install liquid-fire

Slide 68

Slide 68 text

$ ember install ember-simple-auth

Slide 69

Slide 69 text

$ ember install ember-cli-mirage

Slide 70

Slide 70 text

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

Slide 71

Slide 71 text

7. Documentation

Slide 72

Slide 72 text

Learning sub team

Slide 73

Slide 73 text

Ember Guides

Slide 74

Slide 74 text

Slack

Slide 75

Slide 75 text

8. Reliable, regular release cycle

Slide 76

Slide 76 text

(borrowed from Chrome)

Slide 77

Slide 77 text

Every 6-week there is a new release

Slide 78

Slide 78 text

No content

Slide 79

Slide 79 text

Inclusion strategy for new features

Slide 80

Slide 80 text

LTS releases

Slide 81

Slide 81 text

SemVer

Slide 82

Slide 82 text

9. MIT License

Slide 83

Slide 83 text

10. Public RFC process

Slide 84

Slide 84 text

(borrowed from Rust)

Slide 85

Slide 85 text

New features/ modifications have to go through the RFC process

Slide 86

Slide 86 text

Why? Alternatives. How do we teach this?

Slide 87

Slide 87 text

Open Initial comment period Final comment period Close

Slide 88

Slide 88 text

Case Study

Slide 89

Slide 89 text

Deprecate Ember.K

Slide 90

Slide 90 text

No content

Slide 91

Slide 91 text

No content

Slide 92

Slide 92 text

No content

Slide 93

Slide 93 text

Implementation work begins

Slide 94

Slide 94 text

Add deprecation warning to codebase

Slide 95

Slide 95 text

No content

Slide 96

Slide 96 text

Ember 2.11-beta release

Slide 97

Slide 97 text

Provide an easy way forward

Slide 98

Slide 98 text

No content

Slide 99

Slide 99 text

No content

Slide 100

Slide 100 text

Pearls of Wisdom

Slide 101

Slide 101 text

“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

Slide 102

Slide 102 text

“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

Slide 103

Slide 103 text

“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

Slide 104

Slide 104 text

“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

Slide 105

Slide 105 text

“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

Slide 106

Slide 106 text

“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

Slide 107

Slide 107 text

“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

Slide 108

Slide 108 text

No content

Slide 109

Slide 109 text

No content

Slide 110

Slide 110 text

Thank you! https://balinterdi.com/agentconf17

Slide 111

Slide 111 text

References • Framework architecture image from Evan You’s “Vue.js the progressive framework”