[oxryly1]

Racket has a few issues that make it hard to put into a production environment with a team of devs.

* Poor editor support. Apart from emacs and vi, many widely used editors support syntax coloring, but few do any proper indentation, and none (AFAIK) will do anything like intellisense. Only DrRacket really goes the distance on all those points and it hasn't kept up with the likes of Visual Studio Code or Sublime etc. You may say, just use Emacs! But if another dev doesn't use it they'll just ask for the language plugin for their current editor and then be mystified and frustrated at why they can't be productive.

* Poor performance. Out-of-the-box new Racket code will be slow. You can "precompile" it using Racket's built-in tools, which is great. But the process is complex and error-prone, and deploying your "precompiled" Racket code across a team in heterogeneous environment is not straightforward. My teammates are regularly stumped by how to keep our code running quickly. Racket also lacks effective profiling tools to address this.

That said, as Bjarne Strousup opined: "There are languages people complain about, and there are languages no one uses." I have used Racket in production environment for many years.