I don't think that's true at all. I have to go pretty far up the Org tree at my corporate job to get to 300 engineers and that encompasses functionality easily broader than "running Wikipedia" in scope and scale.
I don't think you understand the scale of "running Wikipedia". I do. I worked there for years when there were 100 engineers and they were severely understaffed.
Wikipedia is: mediawiki (and its development), wikimedia cloud services (which I built) that runs tools and provides services for developers (including volunteers and tool authors), server/network infrastructure, wikidata, search, etc.
Mediawiki itself is extremely complicated to build and run, and it's running for numerous languages across multiple projects (wikipedia, commons, wikidata, wiktionary, etc etc).
I'm leaving out a lot of the other things handled by the engineering teams, but it's considerably more complex than you think it is.
I don't think you understand the scale of "running Wikipedia". I do. I worked there for years when there were 100 engineers and they were severely understaffed.
Wikipedia is: mediawiki (and its development), wikimedia cloud services (which I built) that runs tools and provides services for developers (including volunteers and tool authors), server/network infrastructure, wikidata, search, etc.
Mediawiki itself is extremely complicated to build and run, and it's running for numerous languages across multiple projects (wikipedia, commons, wikidata, wiktionary, etc etc).
I'm leaving out a lot of the other things handled by the engineering teams, but it's considerably more complex than you think it is.