For example, from a theoretical computer science perspective of programming languages handling backwards incompatible change is not a hot topic. Or also compiling ergonomics (as a slight counterexample to my own point, stack, the build system for Haskell has a shebang mode where you can take a Haskell source file and transform it into an executable by prefixing some magic comments)
Your wish has been granted: Larry Wall, Perl 6.
> When developing a DSL, people from different areas come together:
> - the application developer who just wants to use the DSL,
> - the DSL designer who develops domain-specific abstractions, and
> - the machine expert who knows the target machine very well and how to massage the code in order to achieve good performance.
> AnyDSL allows a separation of these concerns using
> - higher-order functions,
> - partial evaluation and,
> - triggered code generation.
The only way I could see what you're proposing making sense is if you got the linguist to design a much higher level language that operated on more concrete concepts. Some kind of domain specific language.
It feels like you're talking about Clojure.
I'd love to see language design and language development treated as different disciplines.
Just like developers were the first web designers, developers have been the first language designers.
Ideally a language designer would only be tasked with how to express complex ideas in a simple, composable syntax.
Language developers would be tasked with everything else: basically making those ideas work as efficiently and consistently as possible.
Not to say a language designer and developer can't be the same person, but I think there might be some benefit to having a linguist (with some understanding of development) and a developer (with some understanding of linguistics) team up on a new language.