Ember Template Imports series discussion

[chriskrycho]

I posted the first couple items separately on this forum, missed those in between and have now wrapped up the series with Part 6: Given the tradeoffs in the space, what is the best set of compromises we can make?

So: let’s treat this as a host for further discussion/comments/etc. while I’m working on the RFC (which I expect to have open probably the week after US Thanksgiving)!

• Series page with links to all the other posts
  • Part 1: Introducing the series and walking through the formats.
  • Part 2: Which template imports design has the biggest set of wins for teaching and understanding components?
  • Part 3: Evaluating the tradeoffs of template language designs for tooling.
  • Part 4: Keeping, and improving on, one of Ember’s fundamental commitments — and biggest strengths: its integrated testing.
  • Part 5: What about styles? (A bonus post!)
  • Part 6: Given the tradeoffs in the space, what is the best set of compromises we can make?

As an alternative, you can download the whole series for reading offline:

• EPUB
• PDF

[dknutsen]

Thank you very much for writing all of this @chriskrycho! I really appreciate the time and effort you clearly put in making sure you gave a thorough, detailed exploration of each option and considered pretty much everything. This has been really helpful for my thinking and even more importantly helpful for sharing with others who are less familiar with the proposals/template-import work in general.

[chriskrycho]

It was my pleasure, and hopefully it’ll be useful as I follow these up with an RFC advocating that we stabilize <template> (going to be starting on writing that this coming week!).