Earlier quoted context omitted.
Remote work eliminates the emotional content of the communication channel between workers. That is bad for team cohesion and serendipitous collaboration. Humans have evolved a number of emotions that enable us to work together even when it's not in our immediate self-interest: guilt and shame to realize when we've hurt somebody else and discourage us from doing it again, excitement to pick up on and pile into promisi…
This really sounds like status quo bias to me. No one's going to tell you that face to face communication isn't an incredibly efficient medium, but that doesn't mean teams and companies built around remote work can't (and don't already) thrive. I would even hazard that your experience is possibly colored by the teams you've worked on and the companies you've worked for.
My personal preference, as a developer, is for remote work. But when I look at what the team actually accomplishes, the level of creativity in its solutions, and how quickly it accomplishes them, a colocated team almost always beats the distributed one. There's an energy that you can get when everyone is in the same room that's impossible to replicate when they're 1000s of miles apart.
The cases where I think remote work can do fine is when you have a simple tool or interface that needs implementing, or if you're just trying to optimize one number (eg. performance of a library). These are the same situations you'd use a contractor for.