C'mon. This is splitting hairs. No one doing anything serious, changes their language syntax for their production code overnight. Just think of what this could

C'mon. This is splitting hairs. No one doing anything serious, changes their language syntax for their production code overnight. Just think of what this could possibly mean for those people. They need to retrain their people on the new syntax, new ways of maintaining them and who knows what other regression comes along with it(Test cases, deployment, libraries, performance etc). All of this for 0 gains, when better programming languages committed to maintaining backwards compatibility exist. I think we should settle for the fact that Racket is more like a toy language for teaching purposes. That is ok, given its use case.