Huh? Weird, I have written a blog website in what Racket offers, following the documentation you criticize in another comment and got it working. Even the not so easy to understand continuation based side of it came to me after reading it thoroughly. It is quite simple to setup your REST routes and all that.

If you are interested, you may refer to: https://github.com/ZelphirKaltstahl/racket-markdown-blog/tre...

I did never bring it online, as I never rented a server for it, but it definitely functions and I had some local posts, which I did not include in the repository.

Did you never have a software without documentation? I think that would be way worse than having a sort of OK documentation of a bare bones web framework, that is actually understandable, with careful reading.

The Racket mailing list is also very helpful and people there are helpful in my experience. Show them you tried and your attempt at things and they'll probably help you out. My only pain with it is, that they are on Google groups.

I'm sorry, but it's like complaining that Haskell is not a practical language. If you want to do production work, then why not focus on languages that are geared towards that? There are a lot of choices out there...