@davatron5000 @stubbornella Interesting, but hard to see it flying with the stakeholders involved. Ive seen the benefits of a compile to interchange format, too, but also been scared by it.

Hints of https://xkcd.com/927/ while also being out of date to current web APIs and proposals.

As president of WCs, you should gather a committee to bring it inline with changes over the last six years? Implementors at TPAC DID bring up reviving the Declarative Web Components convo multiple times.

Standards

xkcd

@westbrook @davatron5000 @stubbornella This proposal reminds me a lot of my #HtmlFragments investigation a lot while back (albeit with a very different use case in mind).

https://blog.dwac.dev/posts/html-fragments/

I wonder if there is a potential path for this proposal which is less "Vue in the browser" and more "a primitive SFC format which frameworks can compile to". I wonder if this could solve multiple problems:

1. #SSR small fragments of #HTML after page load.
2. Vertical slice of separation of concerns for a component.
3. Import module format (like #HtmlImports or #HtmlModules).
4. Lazy loading a component and its styles without requiring CSS-in-JS.

Kind of a smorgasbord of requirements but I can see value in the right primitive here.

A Simpler HTML-over-the-Wire - Devel without a Cause

Is it possible to build an HTML-over-the-wire application with only native web technologies? See how far can we go with zero custom tooling, and how the web specification can change to support it.

@develwithoutacause @davatron5000 @stubbornella Monthly #webComponentsCG sessions start on Monday and using some of that time to prep proposals like this for the new quarterly face to face with implementors doesn’t seem like too bad of an idea…

@westbrook @davatron5000 @stubbornella I suspect this might overlap with existing #HtmlModules work.

Also one more idea similar to 1.:

5. Could we use this format to do the initial render of a component? By which I mean that #Angular compiles components to #JavaScript which looks like:

```
function renderComponent() {
if (initialRender) {
createComponentDom();
} else {
updateExistingDom();
}
}
```

This always bugged me as inefficient, because the first branch is only ever executed once per component instance. If we compiled components to this SFC format, could we just do the first render at compile time, generate the HTML directly and drop that `createComponentDom` function?

I'm not knowledgeable enough to say that definitely makes sense, but I think it's an interesting idea at least.

Not sure if other frameworks could benefit from similar optimizations, I suspect #React would not, but I'm less clear on non-#VDom frameworks.