Compilers are biased, among other things, towards: - Having a rich, complicated internal model (and having minimal contact with external data; mostly just the

Compilers are biased, among other things, towards: - Having a rich, complicated internal model (and having minimal contact with external data; mostly just the code being ingested) - Recursion - Being stateless (at the top level anyway; code goes in code comes out) - Having an enormous amount of semi-regular code (favoring macros and related features) - Dispatch/polymorphism among very broad type groups (favoring enums and ways of discriminating enums) Not that any of these things are bad to support in any given language, but every language is a big bag of trade-offs, and focusing on compilers might cause you to choose certain tradeoffs that aren’t as relevant to the way the language will typically be used later on No specific judgements on Rust (in fact, Rust has ended up seeing a lot of use for compilers and compiler-adjacent projects), just something I’ve been thinking about in general