Is this an actual thing that happens / can you point to an example of a tech community getting taken over by someone who lacks expertise in the subject?
The projects I think of as overly subject to corporate control (the Linux kernel, for instance) had the existing technical leadership voluntarily submit themselves to that corporate control, because it suited their desires.
If what you're really trying to say is "It keeps out the SJWs," you have no guarantee that being an SJW is anticorrelated with technical expertise, and there are several highly technically competent SJWs. So you leave yourself vulnerable to a small number of folks who are willing to learn the terminology and develop genuine expertise and then take over consensus in the project, because you've arranged things so that there are so few people deeply involved in the project in the first place.
I don't think he's saying just keep out the sjws. Note that he's aiming it at the "advocates" and other such non technical roles, which he deems as gritfters/parasites.
Funny you bring up the Linux kernel, which has been completely subverted by the likes of Intel and RHEL. Linus was forced out using a slightly unorthodox strategy because his natural disagreeability was an effective defense against traditional subversion strategies. In any case, the strategy adopted by Urbit would probably have worked to protect Linux development from this takeover, but may also have hindered adoption to a degree that Linux would never have come to dominate.
The projects I think of as overly subject to corporate control (the Linux kernel, for instance) had the existing technical leadership voluntarily submit themselves to that corporate control, because it suited their desires.
If what you're really trying to say is "It keeps out the SJWs," you have no guarantee that being an SJW is anticorrelated with technical expertise, and there are several highly technically competent SJWs. So you leave yourself vulnerable to a small number of folks who are willing to learn the terminology and develop genuine expertise and then take over consensus in the project, because you've arranged things so that there are so few people deeply involved in the project in the first place.