Post

I didn't get any credit for the `as` prop back then, which is fair since I didn't invent it. I borrowed it from a library called Semantic UI. But I'd be sad if the same thing happened with the `render⁠=⁠{⁠<⁠Comp⁠ ⁠/⁠>⁠}⁠` API. I invested a lot of time in that.

I mean, there's no need to mention me all the time or anything. Just don't let history be forgotten 🥲

you should write a blog post about it!

related, i remember learning about the "as" from rebass around 2017 or 2018 but I see now that semantic ui had the initial version in 2016 random trivia: they called it "augmentation", before "composition" was cool, they later renamed it 😅 github.com/Semantic-Org...

i love learning about API history, would love to read how you came up with render={<Comp/>} and what were your inspirations then

Yeah, Semantic UI was the first component library I saw that used this prop as a core API for all its components. I created ReAs (React As) as an experiment around this (github.com/diegohaz/reas). This project eventually became Ariakit.

I added support for TypeScript and arrays, and then I renamed the prop to `use`. This was before React hooks. This work now lives in a separate repo for posterity: github.com/diegohaz/reuse

However, the as/use props had several problems. I talk about some of them here: youtu.be/_kyv3tnQKfg?...

Whether `render` is better than `asChild` ultimately comes down to personal preference. But @dio.la listed a few reasons I agree with that make `render` better: x.com/daniguardio_...