Proposal: Programming Language Design
The subject of this proposed site seems to encourage questions that are a bad fit for Stack Exchange. Indeed, most of the (as-of-writing) top-voted sample questions seem either opinion-based or yes/no/list questions (my emphases of opinion indicators and yes/no/list indicators), the remaining ones being general enough to have no single objective answer:
What are the advantages/disadvantages of implementing strings as character arrays?
Is there a widespread alternative to C-style or Python-style code block syntax?
How would you design a compiler upfront to be both a compiler and a Language Server Protocol server?
How could custom infix operators be implemented in a parser?
Advantages of extension methods vs UFCS
How to run a lazy and pure-functional language efficiently?
Could a Rust-style borrow checker work based on compiler inference?
What are the advantages of compiling vs. interpreting a language?
How do I turn this left-recursive grammar rule into a rule that isn't left-recursive?
What are the upsides of using explicit line-ending characters (like semicolons) as opposed to newlines?
How do you check whether an inferred type matches a type signature?
What is the difference between LL (1) and PEG parsers?
Should types be a first class value?
Is such a site a good fit for Stack Exchange, and if so, what are the advantages/disadvantages?