(... various build output ...)
real 13m40.762s user 15m55.635s sys 0m48.083s
This is a quad-core device from 2012 with 8GB ram and a typical non-ssd hard drive.
I find this time to be damning in terms of considering Racket for a production system. Don't get me wrong, I enjoy some features of Racket and have used it for multiple personal PLT sidetrack projects, but how am I meant to deploy something that takes 13m (!!) to build one single package?
I'm spoiled with Go and Python, so I can enjoy very fast speeds in my typical work, and maybe I'm just out of touch with how much the Racket compiler is actually doing.
I'd love to know your feedback, and whether there's some way to speed Racket up.