Re: [w3c/webcomponents] Meet at TPAC this autumn? (#877)

Slightly off topic, but Microsoft would be **very** interested in seeing a document that represents the latest template instantiation proposal and exploring how we can help out in this area.

The area of templating is highly contentious. I have my own opinions, backed by many years of working with communities on multiple frameworks and libraries I've designed. Other framework and library authors likely feel the same. Community members have their own opinions, sometimes even stronger than the library authors.

As a result, I'm mostly interested in starting with low-level APIs and seeing how existing DOM-based frameworks could be re-platformed on top without individual libraries/frameworks being forced down a path they don't feel fits their community. To that end, the new APIs should:

* Support existing libraries implementing the features they have today 
* Reduce library code
* Improve performance
* Reduce memory

Nothing surprising there. It's just important to note that perf or reduced code alone are not necessarily enough. If the new APIs don't help with our real-world features and scenarios or force massive breaking re-design on the community, we'd likely stick to a user-land solution in spite of the new APIs. The 2017 proposal seemed a bit dubious in that some of the low-level details appeared an after-thought in the rush to try to provide a high-level templating solution.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/877#issuecomment-676439144