he/him 
I wonder if it's healthy that when Facebook open sources internal tools, they automatically come out of the gate with a lot of credibility in the React community.
I started the library they're referring to and this was my concern about open sourcing it. Still don't know how I feel about it, but what about it being an "internal tool" do you find problematic for open sourcing? Relay is an "internal tool", so was GraphQL etc.
-
-
It becomes problematic when it's unclear to the community whether they should expect a general-purpose thing, or a tool built specifically for Facebook's needs.
-
Which is exactly why it hasn’t been open sourced yet, if at all. I do believe it is general purpose enough though to warrant potentially a public release.
- 3 more replies
New conversation -
-
-
Just about how it impacts the normal push and pull of library adoption. Maybe it will crowd out a promising approach, or discourage someone from working on a similar approach who doesn't work at Facebook. Not sure, really. Just ruminating.
-
There are similar libraries and I believe any release would actually elevate those too. React has too little opinions and people struggle to build performant apps, styling is a large part of that. One way to deflect some of that criticism is to release our solutions.
End of conversation
New conversation -
-
-
One thought I've had is that big companies have big process, big teams, and big tooling in place, and often when they push out even small tools, they don't seem to work well on their own (outside their original ecosystem).
-
To use them effectively, you're often forced to adopt many other pieces of the parent's ecosystem as well. It's not necessarily bad, but it does create challenges for teams.
End of conversation
New conversation -
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.