Ember Community 2016 - Be the Bark
•
2 likes•1,051 views
For my talk I shared a few recent thoughts about open source communities, how they are influenced by the businesses that adopt their software, and how Ember's priorities can be thought about in 2016. A lot of this talk was inspired by and referenced Larry Wall's essay Diligence, Patience, and Humility (http://www.oreilly.com/openbook/opensources/book/larry.html).
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
More from Matthew Beale
More from Matthew Beale (12)
Recently uploaded
Recently uploaded (20)
Ember Community 2016 - Be the Bark
- 6. Suppose Iwant to take over theworld. Larry Wall, 1999
- 7. Simplicity says I should just take over theworld by myself. Larry Wall, 1999
- 8. But the reality of the situation is that I needyour help to take over theworld, andyou're allvery complex. Larry Wall, 1999
- 9. I actually consider that a feature. Larry Wall, 1999
- 10. I'm still a little bit of the onion. Most of the mass is in the outer layers. But here I sit in the middle. I get a bit of honor for my historical significance, but in actual fact, most people see the outside of the onion, not the inside. Unless they make onion rings. But even then, the bigger rings have more to them than the smaller rings. Let that be a lesson to those of youwhowish to be "inner ringers." That's notwhere the real power is. Not in this movement, anyway. Larry Wall, 1999
- 13. YOUNGEST
- 14. OLDEST
- 15. Larry Wall, 2001
- 16. OLDEST YOUNGEST
- 19. CORE
- 20. BARK
- 21. 2015 2016
- 24. Why the change?
- 29. Consultants 2015 Product dev Company >70 Small business 9 8 1 10 2016 6 8 4 6 Jobs for Ember Core
- 30. More large companies are influencing Ember than ever before
- 31. Large companies need different things than smaller companies
- 32. Large companies need different things than smaller companies Bigger audiences mean a diverse set of devices, which mean performance concerns
- 33. Large companies need different things than smaller companies Bigger audiences mean a diverse set of devices, which mean performance concerns Bigger teams need technology soluWons to organizaWonal challenges
- 36. <aside/>
- 38. • We’re re-implemenWng Glimmer’s algorithm • Moves many of Ember’s template features out of Ember • Google’s V8 engine loathes polymorphism. Get strict about types • Smaller templates • Improved architecture, abstracWons
- 41. API Ember StaWc
- 42. API Ember StaWc
- 45. A universal app
- 47. >
- 50. Every Ember app, a universal app
- 51. • Server-side rendering anyone can use • Provides provisioning and deployment tools (AWS, Heroku, Docker, others?) • CompaWble with Ember 2.3+ • Experimental servers have been stable • You can use it. SWll nailing down details (cookies, content in <head>) • Glimmer refactoring unblocks rehydraWon
- 53. Ember Engines
- 54. • Routable engines • Template mountable engines • Totally isolated. For example, by default services are not shared between an app and engine instance • CompaWble with Ember 2.3+
- 60. • “InWmate” APIs must be deprecated for at least one LTS • Increased stability for addon authors • Slower upgrade cycle for those who want it (twice a year, basically) • An LTS happens every 4 minor version releases • First LTS 2.4?
- 61. Glimmer and FastBoot largely address performance Engines and LTS are technology solutions to organizational challenges
- 62. LESS CORE
- 63. MORE BARK
- 64. MORE BARK Ember
- 67. MORE BARK Ember-Data Ember-CLI Ember FastBoot Engines Glimmer Liquid-fire Guides Ember-Collection
- 70. • Sub-teams will see increased ownership of the RFC process • Sub-teams will have a representaWve on core • Sub-teams should have increased autonomy • Maturing this process is on-going
- 71. The bigger rings have more to them than the smaller rings. Let that be a lesson to those of youwhowish to be "inner ringers." That's notwhere the real power is. Not in this movement, anyway. Larry Wall, 1999
- 72. MORE BARK
- 73. BE THE BARK