Use to be that if there was a nice open source project that solved most of a problem you had, you'd jump on, if you had the ability, and contribute back to it. Now I guess we just wait for random handouts from big companies so we don't have to do any work ourselves. Bit of a shame, the appification of open source, but I guess that's where it's going. Big and supported, with no room for newcomers.
I wonder how this is much different than what people say about net neutrality? Once the big guys are there, they'll actively do what they can to kick the latter down so no upstarts can chase them up it, and I guess this is just as true of the web.
Hope we can find a big company to release us an open source web replacement one of these decades, since I guess we won't be able to band together and build it for ourselves.
I see it as a sign of maturity. People now realize it's completely unreasonable to think about debugging or maintaining some codebase as a hobby themselves (aka: in addition to the product they're building). For a cross-platform dev framework on mobile, knowing the pace at which those platforms are moving, you need something that has both the team , the fund and the stakes.
You're comparing Go to RN. The comparison he's making is Matcha to RN. Matcha doesn't come from a giant company. The language it's in does, but that doesn't mean anything for framework momentum.
We are discussing about the framework itself and not go as a language.
The framework is a nice idea, and will definitely help into diversifying some of the mobile frontend stuff.
On the other hand you can't compare RN to this framework.
As the person you commented on, facebook has been using RN on its main products like instagram, so it has proven that the framework can be placed on production ready apps with a massive userbase.
That's not really a direct comparison. We're not talking about languages here - it's the framework. React Native is used and developed by Facebook, whereas Matcha is used and developed by no one notable (afaik).