Before I started feeling comfortable with the official Racket docs, Beautiful Racket served as an accessible reference as I began exploring the language.<p>I'm turning into a big Racket fan. I just rewrote my website's backend in Racket [0], and I've been learning how to publish packages for the ecosystem.<p>[0] <a href="https://github.com/jacobwhall/jacobhall.net" rel="nofollow">https://github.com/jacobwhall/jacobhall.net</a>
The name Scheme somehow makes sense to me ("in the grand scheme of things"), while the name Racket does not, even though it parallels the alternative meaning of
the word "scheme." ("Matt" would be a more fitting name, looking at the names of the people involved :)
Interesting model, it's an honor system to a read "free" (as in not toll-gated) book on the web, with a starter price of $40 USD. <a href="https://beautifulracket.com/how-to-pay.html" rel="nofollow">https://beautifulracket.com/how-to-pay.html</a><p>I admire the model, and the try-before-you-buy but somehow paying $10 for a book I won't get around to reading ever most likely is a lot more appealing, whereas starting a book knowing that I should pay $40 somehow is off-putting enough to not make me want to try.<p>Good on the author for being creative. Just sharing how my grey mush responds to the whole situation.
I had read the post [1] here on HN at the time, about how he faced abuse in the Racket community, but when posting this submission I did not recognize the author of the book was the one.<p>I'm glad his work hit the frontpage. This would hopefully attract more attention to his work, as well as the problem in the Racket community, if the problem still persists.<p>[1]: <a href="https://news.ycombinator.com/item?id=27531508" rel="nofollow">https://news.ycombinator.com/item?id=27531508</a>