Well I think the discussion is more or less settled now, but the key takeaway is that seemingly small things like this can make a big difference.
Common composition scenarios like this need to have an abundance of examples and documentation. We need to somewhat keep an eye on the API surface of competing frameworks (Angular and Vue in particular, since those tend to be the ones that Aurelia would be considered as an alternative of; React OTOH is kind of a unique beast that needs a different approach), and make sure that the things we also support, are documented properly, as well as their differences to how these problems are solved in other frameworks.
Whether or not @danny’s company decides to go with Aurelia will likely determine whether or not another dozen (or more) developers end up investing themselves in Aurelia, which then propagates onward.
This is not an uncommon scenario and it has to be easy for people to find the right docs/examples. How do you even know what to search for, if you don’t know that
replaceable is there to fill some of the feature gaps of shadow slots?
@Eisenbergeffect are we taking this into account with the new docs?
If we take proper care of this area, it will be much more likely for existing Aurelia users as well as newcomers to stay with Aurelia, and to convince their peers/managers to do so as well.