Retro-justification is not some flaw it is most common way people choose tech stacks.
The only logic that matters most of time is business logic of solution serving problem statement and not logic of choosing a technical stack.
Post hoc rationalization
The choice we made for other reasons is the best one for these constructed reasons that didn't exist until later.
https://en.wikipedia.org/wiki/Choice-supportive_bias
Measuring and Mitigating Post-hoc Rationalization in Reverse Chain-of-Thought Generation https://arxiv.org/abs/2602.14469
The original point was that go is not a Pareto-optimal choice along any set of language criteria.
"I didn't feel like choosing $LANG's competitors, so I went with $LANG" might be how languages are chosen for projects in the real world, but it's not exactly a convincing rebuttal to the argument being made.