Not exactly Racket. But with Perl. And the same argument. Early 2010's, I remember my company had a fairly fast, stable and small(LOC wise) data feed processin

Not exactly Racket. But with Perl. And the same argument. Early 2010's, I remember my company had a fairly fast, stable and small(LOC wise) data feed processing application in Perl. It just worked, barely any bugs, maintained by 2 - 3 programmers. Time came around, and your Director level people realized the teams were too small, programmers were having too much fun and more importantly it made programmers felt valuable and hard to be treated as kleenex. They decided to give some Architect Astronaut love to the application. Then came in Java programmers. Code base size exploded by 500x. Design pattern floods followed. DI to manage complexity which shouldn't have even existed. Hundreds of classes to do things that could be done in hundreds of lines in Perl. Managers routinely boasted how they managed to grow their teams, about their culture, and how big and great their teams were. They could never make it work as well as it did in Perl. I too moved on. But eventually I saw they just shut down the product. No manager likes to see their work less valuable or better than that of a programmer. Languages like Perl, Scala, Clojure, Racket, Common Lisp are never going to see decent adoption in the industry.