Alex Matchneer

This functionality is here to stay, as it is very important for interop with the rest of the non-Task world. I suppose we could improve the docs surrounding this functionality...

@SirZach that sounds like a perfectly reasonable use case to add to the docs 👍

@bnetter we're blocked on angle bracket syntax landing in Ember. Til then, emblem bindings will behave as they do in Ember Handlebars/Glimmer when using curly `{{x-component foo=bar}}` syntax: `foo` will...

Ah this is so cool, thank you so much! The shield with glasses looks pretty awesome, I think I'm sold, but hey if other people are curious to get in...

So if I wanna throw this up on the site, what kind of attribution would you like? Would be cool to also get some shirts.

Work on this should be finished within the week with the next version of Emblem; progress can be tracked here: https://github.com/bantic/emblem.js/tree/ember-cli

What's the use case for client compiling if you get server precompilation for free?

I can't think of a good reason to set handlebars.precompile to false. Note that this is different than the `rake assets:precompile` task, which will precompile your assets into the `public/assets`...

@mreinsch how is that true? Regardless of whether you client-side compiled or precompiled, you're still going to be stepping through the Handlebars VM' stack, right? (This code admittedly looks like...

@mreinsch ah, I see. Seems legitimate. I'll try to get to this shortly.