It's a "feature" of SE I think.
When asking the question, you need to know enough about what you're asking about to be able to phrase the question in a "tight" way.
I think this is a pity, since people who need the most help, people whose question is basically "I don't know what's going on here, can somebody help me?" (i.e. a very "loose" question), naturally fall foul of this.
It's particularly ironic because the people who frequent the SE sites have an enormous wealth of knowledge, and probably could help you, if they were so inclined. And then there's the objective (good) versus subjective (bad) argument - I'd suggest that possibly the most useful answers on here are subjective, because they're based on peoples' real-world experience.
But on the flip side, especially when the question is "what bike should I buy?" you can imagine there could be hundreds of permutations that come into play. Maybe something as trivial as what colour you want the bike to be. So how do you safeguard against a thousand "what bike" questions appearing, all basically the same but with subtle differences?
I think the trick you bear in mind is that when you ask a question, people will look at it not so much as how the answer will benefit you, but how it could also benefit the next visitor, the visitor after that, the visitor coming along next year etc. It's quite amusing because you realise you have a knowledge-base site whose primary goal is not be be a knowledge base, but to keep itself spick and span. But for better or worse, that appears to be SE policy.
If its any consolation in your particular case, by the time you buy your second bike, you'll know exactly what you want!