Practically every large open source project is coordinated over the internet with limited face to face time, so the concept works well at some level at least.
Given that the model works in theory, it's surprising there aren't many startups trying to go the last mile to make remote working better for a general audience.
Similarly, web programming was over a decade old when Rails was started. You could build Rails as an open-source project. You couldn't build, say, LoudCloud, or Netscape, or Google, or ViaWeb, or any of the other web 1.0 companies where the process of building webapps was not well-understood.
Virtually all profits in the tech industry are made by companies with a short-term monopoly on the technology involved. By the time a problem-domain is solved well by an open-source project, by definition, there is no money in it. Ergo, teams that want to make a lot of money will work on projects where communication costs make remote work very challenging.
Also, the project lead in such project don't pay that distributed team and is not responsible for their effectivity nor turnover, hiring, promotions, salary negotiations etc. Majority of Linux kernel developers are paid for development, but they are paid by various third party organizations.
A full remote team has a big handicap on that.