Proposal: Programming Language Design
We've currently got a lot of questions formatted as "should I/my language [...]", such as:
- Should I have the concept of a "statement" distinct from a expression? Why or why not?
- Should types be a first class value?
- Should my language have a type for single characters?
- Should a CAS (Computer Algebra System) distinguish between mathematical variables and programming variables?
There are just as many "how should" and "when should" questions. A lot of these have been getting close votes, and comments suggesting that the wording be changed to something more objective. Since this seems to be a common form of question, we should probably form a policy on dealing with them now.
The main issue with "should" questions is that they're perceived to be subjective, and likely also depend on information specific to the asker's situation rather than more generally applicable, and invite binary yes/no answers. However, they can be pretty easily reworded to a question about the advantages and disadvantages of a feature, which has happened multiple times, so maybe allowing "should" along with or as a shorthand for "why or why not" (like in the first linked answer) is an option.