Emi

Yeah my research basically uncovered that those blink IDL files would provide: 1. All of the JS type names (`HTMLBodyElement`, equivilents for svg, etc). 2. All of their properties (`href`...

Yes, I think there should be recommendations and tooling here. There are different layers to Vecty: its core (what exists today, and what I view @pdf as discussing above) and...

This gets asked a lot, what @VinceJnz said seems all accurate though, but actually there's a very simple answer. * Does the parent component own choosing the value of the...

Oh interesting, I did not think of that. Indeed, that's a bit better! --- I am also wondering what drawbacks there would be to: ```Go func Tag(tag string, children ...vecty.ComponentOrCHild)...

Interesting ideas. I think that in general it is better to strive to be functional in nature and avoid mutability where possible, because more state == harder to reason about...

> I don't think we can entirely avoid the need for JS lib interop I completely agree with this. in fact, I don't think we should try to avoid JS...

I guess what you are saying may be that, currently it is not possible to get a reference to the DOM node for the element that your component returns from...

Ok, so for now I think we will absolutely have a `WithChildren` and `WithMarkup` specifically for JS interop ala #78 -- just wanted to state that & say that we...

> If slot is `nil` for first render, you have an indeterminate state. I don't think it would be indeterminate; it would depend on what we now have. To give...

A more simple thought: we could do as you originally proposed and outright ban / panic on `nil`.. don't know why I didn't think about zero-value struct values being a...