Post

- what would that look like? - why are they needed given the ability to pass JSX as a prop?

> why are they needed to better align with one of the platform things that is pretty ergonomic. > what would they look like in jsx? no clue. JSX (as is) isn't isn't flexible enough -- it's kind of a lossy format, as JSX + React doesn't differentiate semantics from any of the props.

Like, just by looking at props, you can't *know* how it's going to be used. With a slot, you can only pass markup / components, etc. It's a narrowing of API without runtime checks

I would argue that React already has slots with a different syntax via component props. It's not a perfectly ideal syntax, but, arguably, it's better than the string-matching chaos of web components. After all, I can write <ProfileCardRaw name="BellCube" description={<p>A very cool person!</p>} />

Imo <ProfileCardRaw description={<p>A very cool person!</p>}/> (especially if there are more props/render props!) is a lot harder to read/parse than <ProfileCardRaw> <p slot="description">A very cool person!</p> </ProfileCardRaw> This is an opinion, other peoples opinions may differ.

perhaps, I think that's only really true if you have one or few props. when you have many, it's nicer to more quickly see slots imo. but for slots, I'd do this syntax:

The problem you mentioned about knowing how it'll be used is a problem of the docs, not a problem of the syntax. Slots don't tell you how they'll be used any better than component props do, since all you see is a name and some magic syntax. Even a simple JSDoc comment over the prop definition works.