But I get that maybe that approach wouldn’t really work. I guess I’ll take the L on this one

Still, not trying to be too stubborn, but in another universe I’d prefer something that feels more natural to me, like an API similar to HOCs, memo(), for example, in terms of syntax, not internal behavior.

Yeah, I get the benefits of string directives and how they make things easier. That makes sense to me and I get why the string directives approach was chosen.

Thanks for taking the time to reply and share more about it. It’s cool to talk with people who build the tools I use every day. Curious to see what the React team is cooking next.

I’m still not a big fan of string directives (even though I use them daily, they still feel a bit magical to me, maybe because it’s a relatively new feature and I might change my mind over time). I read the RFCs you shared and got better context about the decisions behind them.

nvm, you already answered me on the other site 😅

Hey, writing here too

Not a React hater. I use it every day and appreciate the team’s work, but sometimes it feels like the team struggles to accept community feedback on questionable calls, especially with the string directives

bsky.app/profile/knop...