Much questions include a requirement about pricing. For example, a program should be free or "no more than $50".
I understand that the price of a piece of software is relevant in deciding which product to choose. However, making the price a requirement in the question drastically limits the possible answers.
One issue might be that some software costs a bit more, but is well worth the money if you know the advantages. For example, I personally use the file comparison app Kaleidoscope (for Mac), which costs $70. If I didn't knew about this app and I'd post a question here asking for recommendations for diff apps, I would've set a much lower price limit (like $20 max, because it's pretty simple software). However, the fact that I knew how great this app works, made me decide to pay much more than I might've planned on before.
Furthermore prices in questions will make the answers less relevant for other people. Let's say someone asked for a program that's no more than $50. I'm looking for the same kind of software and I stumble upon the question, however, I'd be willing to pay $150 for such a program. Should I open a new question with the exact same requirements, but a different price? If so, that will lead to much duplicate questions and fragmented answers. If not, how could higher priced programs ever be recommended?
I think there are three possible approaches regarding price limits in questions:
- Price limits, as they are used now, are allowed.
- Hard price limits are not allowed, but we introduce soft limits/categories. Maybe something like "personal" and "business" pricing levels. Or something like "USD XX", "XXX", "X,XXX", and "XX,XXX" levels.
- Price limits are not allowed. Answers may contain recommendations for programs of all prices.
Also relevant: How should we handle software prices? about including prices in answers.