To me, the close tie to academia is why Racket is developed the way it is developed.
It is feasible for tenure track academics to use Racket development as a research vehicle to help navigate publish or parent. This makes it feasible for students to use Racket development as route to an academic credential. In turn, the academic context feeds the Racket ecosystem with new novel projects.
Finally standards within the Racket community favor a pedagogical rigor and non-auto-generated documentation.
It is feasible for tenure track academics to use Racket development as a research vehicle to help navigate publish or parent. This makes it feasible for students to use Racket development as route to an academic credential. In turn, the academic context feeds the Racket ecosystem with new novel projects.
Finally standards within the Racket community favor a pedagogical rigor and non-auto-generated documentation.