That's also a classic BS response in Stack Overflow and such.
Someone asks "How do I do X?"
And people will jump to comment "You shouldn't do X, etc" instead of answering the question (and if needed, adding a caveat that they don't recommend it).
Many times people very well know the drawbacks of X, that it's considered a bad practice, etc, and also how to do it "the right way", but want to do X anyway for some specific reason (hacking, working around some issue, etc).
https://en.wikipedia.org/wiki/XY_problem
So it's not so much of a "BS response" as a rational first response, even if frustrating for people who don't fall in that category.
These are people who make bad assumptions when they answer questions.
The point is they're not bad assumptions, they're a pretty good prior. If you swing the other way and assume people "know what they're doing" and take their word for it, you're going to give them and yourself a lot of grief in a majority of cases ("but how do I put the gasoline in the chainsaw to cut the chicken?").
It’s one thing if you are on the DIY Stack Exchange and ask how to knock out a wall, and the best answer is, “That’s a load-bearing wall. You don’t knock it out.”
It’s another thing entirely when you ask innocuous questions like, “How do I tell what web browser and version my code is running in?” and some smartass answers, “You should be using feature detection.”
It’s really frustrating to ask a straightforward question and to get a response from five different people making invalid assumptions about what problem you’re trying to solve. It makes the community seem downright hostile! You may think that you’re addressing the underlying problems—but what you’re doing is telling people, “I don’t take your questions seriously; I know better than you.”
That might not be the message you want to send, but if you rely on assumptions then it will be the message that you do send.
While this can sometimes be annoying, this is actually one of my favourite things about Stack Overflow. Because it means you can ask a really naive question, and actually come away with knowledge of what best-practices for your high-level problem are.
The same question in different context may have completely different answers, yet StackOverflow is all about finding the "correct" answer, and closing "duplicate" questions.
As with nearly every other aspect of modern life, people are at the mercy of a system of rules whose rewards don't exactly align with the benefit of the people in it.
I see variations of this with other fields as well. People disparage college operating systems and programming language classes, because "we have plenty of those already" or say that people should contribute to an established project of some kind instead of reinventing the wheel. But that's how you gain an understanding of how a piece of software works, or how you end up with a new thing that's better than the old one.
Though i do not think any of them is interested in working in games nowadays.
The perfect answerer would have expert knowledge and the free time and an omni-directional goal to serve all questioners. Those people aren't out there.
Someone wants to make a game engine, or asks for help with some aspect of making a game engine, and someone will often reply by saying “you should just use Unity” or something similar. It may be well-intentioned and they may give good reasons why you should just use engine X instead of rolling your own, but here’s the big problem…
Before you help someone, you gotta understand what their motives are.
The next part is simple—if you’re under no illusions that you are not making money by making games, the kind of dollars/time input, salable product output efficiency ratio just stops being relevant. So some other factor is relevant, if you are a hobbyist.