

Sorry, I used “real-time” fairly loosely. I didn’t mean it in the sense of a real-time OS (hard deadlines), more in the sense of “fast updates” (like a chat server). Go is great if you want very low latency in a highly concurrent system since task-switching is so lightweight.
Let’s look at Linux, for example, which is perhaps the most successful FOSS project in the world. It takes contributions from people of a wide range of motivations, such as:
And so on. The net result is a solid, general purpose kernel and a rich ecosystem of supported software. All Linux did was focus on technical details and largely ignore the source.
In the words of Linus Torvalds:
Does it really matter who those eyeballs belong to? Yes, we should be careful about malicious intent (e.g. xz scandal), but that’s a technical problem, not a political or cultural one.
At the end of the day, everyone is free to associate or not associate with any groups they want. If you’re a maintainer, that means you get to decide which contributions you accept and who you let into your communication channels.
I use software maintained by people I really don’t like, such as:
I’ve also contributed patches to some of those as well. Why? Because the technical merits of those protects is pretty much all that matters. If the maintainers go off the deepend and piss people off, I or someone else can fork it. That happened with various OpenOffice (LibreOffice), ownCloud (NextCloud and OpenCloud), and now Redis (Valley), though those had more to do with licensing changes than technical project direction.
That’s why I’m concerned when projects put non-technical concerns (say, a COC) above technical concerns. Yes, civility is expected, and enforcement of that is a lot easier when the project focuses primarily if not exclusively on technical concerns.