It’s seemingly unpopular among the React team 
-
-
Not really. I think we agree with this. However we also believe that you can’t deliver a whole solution if you don’t actively use it. A model that seems to work is promoting full-box setups like Next.js and Gatsby and working closely with them.
8 replies 4 retweets 143 likes -
> A model that seems to work is promoting full-box setups like Next.js and Gatsby and working closely with them. I don't really see that as any different from React having no opinion, which you seem to disagree with.
2 replies 0 retweets 5 likes -
I think saying “you should often/usually use this thing” counts as an opinion?
1 reply 0 retweets 5 likes -
It's a deference of opinion, which I guess is an opinion.
1 reply 0 retweets 3 likes -
We intend to work more closely with communities of these solutions over time btw. So it’s not just deference. I agree current situation is far from ideal.
1 reply 0 retweets 11 likes -
I'm not blaming React at all. I feel like React Native do something similar with Expo and the other more frameworky RN solutions. I think there's cons on all sides of "no opinion", "strong opinion", and "deferred opinion" so have zero actionable recommendations haha
3 replies 0 retweets 15 likes -
I think we usually start having an opinion when it matters for other things. For example concurrent mode might add constraints to preferred styling solutions.
2 replies 0 retweets 12 likes -
Replying to @dan_abramov @sebmck and
Can you please explain why this would be the case?
2 replies 0 retweets 1 like
I worked on a styling library where it was a problem. If you’re injecting styles during React render then you can get into layout and style recalculation issues. It’s due to concurrent mode splitting renders between multiple frames which causes multiple recalculation.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 