$30 off During Our Annual Pro Sale. View Details »

Why Ember 2.0

Why Ember 2.0

Jeremy Mack

August 27, 2015
Tweet

More Decks by Jeremy Mack

Other Decks in Programming

Transcript

  1. What is this This talk is about four years of

    paychecks Look at code on your own A format for feelings and opinions If you’re interested, write a toy app
  2. Why Ember? Rails-like Community Guides Twitter Discourse Slack Codified Patterns

    Router = Router Addons = Gems Ember Data = ActiveRecord Good marketing Design emphasis Open communication Great for building the current generation of web apps Rails was great for CRUD Ember is great for the next complexity level of apps Easy to hire and train for Ember apps feel like Ember apps Developers who know Ember are on the cutting edge Not true of other client-side options I did it this year Release cycle “stability without stagnation” Chrome’s release cycle 2.0 just removed deprecated functionality 2.x Release Process LTS Less frequent upgrades Aware of the state-of-the-art Glimmer was a reaction to React Data down, actions up ES6 Promises Modules RFC Process Addons EmberAddons.com Code sharing built in Even within your own app Ember CLI State-of-the-art build tool Testing built in Advanced features Asset digests Addon installation Package version currency checks Scaffolding Addons Files Bower, NPM, Vendored Assets Upgrading to the latest version is part of the tool You won’t invent Ember The act of writing code is hyper focused Good frameworks codify patterns observed over time by a community Ember has been influenced by a plethora of applications built in it
  3. Rails-like Community Guides Twitter Discourse Slack Codified Patterns Router =

    Router Addons = Gems Ember Data = ActiveRecord Good marketing Design emphasis Open communication Great for building the current generation of web apps Rails was great for CRUD Ember is great for the next complexity level of apps Easy to hire and train for Ember apps feel like Ember apps Developers who know Ember are on the cutting edge Not true of other client-side options I did it this year
  4. Great for building the current generation of web apps Rails

    was great for CRUD Ember is great for the next complexity level of apps
  5. Easy to hire and train for Ember apps feel like

    Ember apps Developers who know Ember are on the cutting edge Not true of other client-side options I did it this year
  6. Ember CLI State-of-the-art build tool Testing built in Advanced features

    Asset digests Addon installation Package version currency checks Scaffolding Addons Files Bower, NPM, Vendored Assets Upgrading to the latest version is part of the tool
  7. Release cycle “stability without stagnation” Chrome’s release cycle 2.0 just

    removed deprecated functionality 2.x Release Process LTS Less frequent upgrades
  8. Aware of the state-of-the-art Glimmer was a reaction to React

    Data down, actions up ES6 Promises Modules RFC Process
  9. You won’t invent Ember The act of writing code is

    hyper focused Good frameworks codify patterns observed over time by a community Ember has been influenced by a plethora of applications built in it
  10. React Very interesting Energetic, dispersed community Crazy early adoption of

    ES6, 7, 8 Impossible to ignore React-Native GraphQL and Relay ABE Lower learning curve It is Facebook
  11. Ember Talk What is this This talk is about four

    years of paychecks Look at code on your own A format for feelings and opinions If you’re interested, write a toy app React Very interesting Energetic, dispersed community Crazy early adoption of ES6, 7, 8 Impossible to ignore React-Native GraphQL and Relay ABE Lower learning curve It is Facebook Me Talks Why Ember? Tapas with Ember fnd How I Learned Ember Apps Beatport fnd.io Once a Month Meals Toy apps Government Why Ember? Rails-like Community Guides Twitter Discourse Slack Codified Patterns Router = Router Addons = Gems Ember Data = ActiveRecord Good marketing Design emphasis Open communication Great for building the current generation of web apps Rails was great for CRUD Ember is great for the next complexity level of apps Easy to hire and train for Ember apps feel like Ember apps Developers who know Ember are on the cutting edge Not true of other client-side options I did it this year Release cycle “stability without stagnation” Chrome’s release cycle 2.0 just removed deprecated functionality 2.x Release Process LTS Less frequent upgrades Aware of the state-of-the-art Glimmer was a reaction to React Data down, actions up ES6 Promises Modules RFC Process Addons EmberAddons.com Code sharing built in Even within your own app Ember CLI State-of-the-art build tool Testing built in Advanced features Asset digests Addon installation Package version currency checks Scaffolding Addons Files Bower, NPM, Vendored Assets Upgrading to the latest version is part of the tool You won’t invent Ember The act of writing code is hyper focused Good frameworks codify patterns observed over time by a community Ember has been influenced by a plethora of applications built in it
  12. /Ember Talk/Me/Talks/Why Ember? I was so excited for ember, I

    built it in Ember with live code samples. http://mutewinter.github.io/why_ember/#/slides /Ember Talk/Me/Talks/How I Learned Ember https://www.youtube.com/watch?v=LyHK18s9taM /Ember Talk/Me/Talks/Tapas with Ember https://www.youtube.com/watch?v=BP7lTpNfkyU /Ember Talk/Me/Talks/fnd https://www.youtube.com/watch?v=i1_aBX8web4 /Ember Talk/Me/Apps/Once a Month Meals https://onceamonthmeals.com /Ember Talk/Me/Apps/fnd.io https://fnd.io/ /Ember Talk/Me/Apps/Beatport https://www.beatport.com/ /Ember Talk/Why Ember? https://www.google.com/url? sa=i&rct=j&q=&esrc=s&source=images&cd=&ved=0CAcQjRxqFQoTCLCJ6pTAyccCFYpWPgodTIcApw&url=https %3A%2F%2Fgithub.com%2Femberjs%2Fember-inspector%2Fissues%2F31&ei=YiLfVdejJInp- QGYyYoY&psig=AFQjCNFusd6O56gm5p376DRSAdkY6bPpHA&ust=1440773092577729 /Ember Talk/Why Ember?/Rails-like/Codified Patterns/Router = Router Every app needs one. It’s your API /Ember Talk/Why Ember?/Rails-like/Codified Patterns/Ember Data = ActiveRecord https://github.com/emberjs/data /Ember Talk/Why Ember?/Rails-like/Easy to hire and train for/Not true of other client-side ... Backbone, for example, has its own way to everything. React, bring your own data model and router /Ember Talk/Why Ember?/Rails-like/Community/Guides http://guides.emberjs.com/v2.0.0/
  13. /Ember Talk/Why Ember?/Rails-like/Community/Twitter The core team is on Twitter and

    very responsive /Ember Talk/Why Ember?/Rails-like/Community/Discourse http://discuss.emberjs.com /Ember Talk/Why Ember?/Ember CLI http://www.ember-cli.com /Ember Talk/Why Ember?/Addons/EmberAddons.com http://emberaddons.com /Ember Talk/Why Ember?/Addons/Even within your own app I’m much more likely to merge something that’s completely decoupled from the app via an addon. /Ember Talk/Why Ember?/Release cycle Might not seem important, but it’s really important long term. This is also something that I had no idea was important three years ago. http://emberjs.com/builds/ /Ember Talk/Why Ember?/Release cycle/Chrome’s release cycle http://emberjs.com/blog/2013/09/06/new-ember-release-process.html /Ember Talk/Why Ember?/Aware of the state-of-the-art/Glimmer was a reaction to Reac... https://www.isemberfastyet.com /Ember Talk/React https://www.google.com/url? sa=i&rct=j&q=&esrc=s&source=images&cd=&ved=0CAcQjRxqFQoTCISahLK_yccCFYFvPgod66UKsA&url=http %3A%2F%2Fblog.tryolabs.com%2F2015%2F04%2F07%2Freact-examples-mailbox%2F&ei=liHfVYT3F4Hf- QHry6qACw&psig=AFQjCNGhQh1U2RtaEvSNuVPbRopSMJZ1vA&ust=1440772884241726 /Ember Talk/React/Impossible to ignore/React-Native https://facebook.github.io/react-native/ /Ember Talk/React/Impossible to ignore/GraphQL and Relay http://facebook.github.io/react/blog/2015/02/20/introducing-relay-and-graphql.html
  14. /Ember Talk/React/ABE Always be experimenting We can experiment with the

    exact tools and environments we use every day. /Ember Talk/Me https://twitter.com/mutewinter