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 🥲

0 reposts12 likes

Alright, before this escalates, let me clarify that I'm just thinking out loud about a minor issue. I dislike this kind of drama and would hate to be involved in it. I enjoy discussing API design and history, though. So here's a good follow-up:

Haz@haz.dev

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 have a draft blog about all the component replacement APIs we considered for Base UI and why we settled on render prop. Will give credit to the people who came up with those APIs in the post. Will post it after xmas.

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.