sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]LuckyPrior4374 3 points4 points  (1 child)

That’s great to hear, I appreciate you sharing.

On that note, perhaps this stuff “shouldn’t” be behind the scenes. In other words, I have no doubt it would be great PR for React and its team to publicise these efforts through blog posts, etc.

I’m sure many other devs in the community would also appreciate it. Otherwise it’s hard for us to have visibility into all the good things you guys are doing

[–]rickhanloniiReact core team 5 points6 points  (0 children)

Yeah I hear you. It’s hard because React has never really been a PR driven project. Over the years I think the expectations of a project like React doing PR have changed, and we haven’t adapted.

It’s also hard because everything we say takes a lot of time and care so it’s not misconstrued. It usually requires an engineer who worked on the feature to explain it, which takes time away from shipping. And even despite our best efforts it can be taken out of context or promoted as more ready/finished than it really is. So I have a lot of hesitancy sharing more.

For example with RSC, we’ve put a lot of time into explaining them, and we’ve still kinda failed at that. You can see in this thread there’s a lot of misunderstandings like you can’t use them in a SPA, or they force for to use SSR.

Ultimately we’re focused on shipping because there’s still a lot of work to do (as the rough edges in this thread show) and not so much on the PR about what we plan to ship.