Because what I'm saying is objectively true: physical colocation with your coworkers is inherently easier to work with than working remotely and no one in their right mind disputes that. The best you can argue for WFH-first is that it can be made to work.
Your other clue is the choice of language. I said, for example, "I hate WFH" and (paraphrased) "I like having a catered office". These are my personal preferences. You can't really argue that it isn't my personal preference. You can argue that those preferences don't work for you, which is 100% fine and indisputable.
In comparison, so many things I see written about WFH are stated with broad generalizations of "WFH is better because ..." when you can clearly tell that really means "I want to WFH and I'm going to argue my preference as being a general good".
You've had other people in this thread and elsewhere agree that a mixed WFH/in-person team is (to quote another commenter here) "the worst of both worlds". If you take that as true it then means that for people to most effectively WFH they need everyone else they're working with to do it as well. It's intellectually dishonest.
To be clear, if you can make WFH work for you and you like doing it, great. I hope you find an employer who works like that or will allow at least some of the team to work remotely. Prognostications that Covid-19 will lead to some seachange in WFH-first employment strikes me as unsubstantiated wishful thinking however.
Just go and look at all the blog posts and articles written about how to make WFH work. Why aren't there just as many (or more) articles about making WFO (Working From Office) work if the benefits are so self-apparent?
There are certain kinds of work that could be remote and would be just fine to do so but they still generally aren't (eg call center work; apart from obvious offshoring cases, a lot of US domestic call center work is still from an office for some reason). But I don't put software engineering at scale in that category.