The thing is, the skill level required to properly manage remote employees, especially in a mixed remote / non-remote office is higher. When you are large corp

The thing is, the skill level required to properly manage remote employees, especially in a mixed remote / non-remote office is higher. When you are large corporation and have to start looking at employees in a statistical manner, you might choose 'no remote' because it's cheaper / more possible to find managers that can do 'no remote' vs. 'mixed remote'. There is almost no large company that is remote only right now. It's the same reason why almost every company programs in blub vs. lisp, haskell, erlang, etc. The skill level of employee can be hard to find who can do those things. Companies already feel supply constrained with engineers, now imagine you add the haskell requirement and you need to hire 1000 of them. Startups can leverage this disadvantage sometimes by not having a statistical management requirement and start with a foundational advantage. There is also the case of using haskell killing your startup although because of tool problems, and big companies being able to make small special R&D type teams that can use Haskell, so it's definitely a balance.