5 ms·

I think maybe the parent comment is wondering "Why Glimmer and not React for the rendering library?"

• wycats 11y ago
  We talk about this a bunch in https://www.youtube.com/watch?v=qwIyenCaSXk https://www.youtube.com/watch?v=qwIyenCaSXk The TLDR is: * We like templates, and were able to implement a more efficient algorithm using them (even more than the recent improvements in Babel). * Compatibility is important to us, so HTMLBars was going to be a much better transition story for Ember 1.x than JSX. * We prefer an HTML-centric templating story (copy/paste valid HTML and it works) over an XML strategy that requires camelCasing, className/htmlFor, etc. * We optimized Glimmer for a hybrid (rerender + subscriptions to the model or service layer) model that can opportunistically avoid work based on knowledge we have from the whole stack.
  • seivan 11y ago
    The Youtube video just says "Please stand by.".
    • wycats 11y ago
      Whoops: https://youtu.be/msS-3zqKKUI?t=51m5s https://youtu.be/msS-3zqKKUI?t=51m5s
  • mrcwinn 11y ago
    Fair enough, but I would argue JSX is just as "HTML-centric" as anything Ember has implemented, so long as we agree "HTML-centric" means, practically speaking, "not HTML."
    • wycats 11y ago
      What I mean specifically is that if you copy and paste some valid HTML from inside a body tag, it will work. That is an explicit non-goal of JSX, and it shows.