I can't speak for others but for me I feel it would have helped a great deal in enabling me to quickly figure out how it was supposed to actually be used. What was tripping me up the most I guess was 1) it appeared to me I needed to use the brackets like shown in the documentation, and 2) that it was wanting some keyword (like "message") there.
Except for that I rather do feel so far that it is a great language for beginners to learn and it even appears that it is in part aimed at beginners in spite of the fact it is a language that professional scientist types developed. It's a bit of a shame there are few serious, well done video (YouTube) tutorials covering vital aspects like how to get a simple GUI for an app put together - which for the most part is surprisingly simple to do compared to other languages I've experimented with up until this point. I had been fiddling with Python prior - which, as you'd expect, has a massive amount of community material out there in the void - but I wandered onto Racket and, except for the documentation snafu I experienced, I find it to be an incredibly appealing language. On Wednesday, November 20, 2019 at 2:31:21 AM UTC-6, Jack Firth wrote: > > Would it have helped if the get-directory documentation had included > examples? Many parts of Racket's documentation are lacking in example code, > especially the less-commonly-encountered parts. > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/700cdde3-38a4-4f3e-b1f8-ba2dcb583bb4%40googlegroups.com.
