What can I say? This is my goal every time.

Thanks for having me!

A huge shoutout to our amazing speakers for sharing their knowledge and inspiring talks: @ryansolid.bsky.social, @kentcdodds.com, @thepunderwoman.com, @lydiahallie.com, @thealexlichter.com, @victorsavkin.bsky.social,
@ryansolid.bsky.social, @phenomnomnomin.al, @wordman.dev, and Luca Mezzalira 👏👏👏

Our panelists are:

◇ @evanyou.me - Creator of Vite
◇ @biilmann.blog - CEO at Netlify
◇ @ryansolid.bsky.social - Creator of SolidJS (remote)
◇ @tannerlinsley.com - Owner at TanStack
◇ @thepunderwoman.com - Angular Team

Hosted by @sarah11918.rainsberger.ca & @thealexlichter.com!

Yeah, absolutely, and I know that's frustrating to not know and not have any visibility other than our comments responding that it's breaking or needs a migration.

Sometimes we don't even know how breaking a change is at first. Many times we do, but even then it might be nuanced. Sometimes we didn't think it was breaking, land it, then find out it broke a ton, and have to roll it back. But yeah, otherwise I agree indicators would be nice.

We do our best to communicate our reasoning, but we get some people who are very upset. We see the passion. It's not easy to say no to someone. Just know there are real people on the other end.

The point I'm making here is that if a PR is closed, it's not because it's personal. It's also not because it's not a valuable fix. It's also not because "We just don't want to improve X, Y, or Z". We always do. We just sometimes can't, and it may not be immediately clear why to the contributor.

Yeah, exactly the kind of thing I mean. Additionally, we WANT to land contributor PRs. We're thrilled people are contributing. We also totally recognize the passion people have for the right solution. We wish it was always as easy as approve and merge.

We get the occasional contributor that gets upset when their issue / PR is closed, and I really wish we could show them the details of how hard it would be to land their change. We're truly not rejecting it for no reason.

Wonderful! Always great to hear! ♥️

Pshhh... But that requires effort... 😉

This is also my hunch. I don't think it causes reflow. What's strange is it will return an empty array if something else has caused a recalculation of styles. It feels somewhat unsafe to use because of that.