I figured you might be. ;)<p>&quot;But what you&#x27;re suggesting requires persuading a large group of developers to adopt a new language -- if you have a recipe for doing that, lots of people including me would love to learn it.&quot;<p>What I&#x27;m suggesting is a group of people interested in trying something and reporting the results try something and report the results. You don&#x27;t <i>have</i> to convince anyone of anything as you&#x27;re responsible for you, not them. :)<p>All you&#x27;d have to do is make sure the tutorials&#x2F;guides, tooling, core libraries, and distribution are in order. Optionally a little bit of evangelism for awareness. Random person on forum or HN: &quot;Hey, I&#x27;d like to try to write some business code or some service in a new language. What should I use?&quot; Drop a Racket link, guide, and something on macros &amp; live updates (if racket has it). I remember loving those when I played with LISP back in the day. I wouldn&#x27;t expect any more from the Racket team.<p>Now, I&#x27;ll drop Racket references in these tangents if you&#x27;re saying you all sat around in Plato&#x27;s Cave with no exposure to real programming past its shadows in academic papers and just came up with everything in Racket on your own. Just seems like there&#x27;s some feedback loops in there from useful projects that caused improvements that make it more useful in practice. If you say no, I&#x27;ll concede I&#x27;m wrong given you&#x27;re part of the core team. Then be mystified at its evolution.