I can think of some reasons you might not want to build it on Racket. I think Racket is fantastic, but if you are developing some novel variety of Scheme or wha

I can think of some reasons you might not want to build it on Racket. I think Racket is fantastic, but if you are developing some novel variety of Scheme or whatever then you might want to have control over "low level" (I'm sorry, I dislike that term) details like how closures get allocated or the evaluation order of things. It's perfectly cool to use Racket to write the implementation of such things though, but maybe as a more traditional language implementation. Of course you're right that it's much smarter to let other people solve the problems you don't care about, so most of the time Racket would be a sensible platform to build on top of.