Why implement a language on top of Racket? A great overview of the advantages from the author of Hackett: https://lexi-lambda.github.io/blog/2017/01/05/rascal-is-now-hackett-plus-some-answers-to-questions/
Related Posts
I'm still tinkering with the website for my PL experiment. I want the styling to express "labour of love hobby project".
Choosing what program to show on the home page is really hard too. All the keywords are links like Racket.
What do you think? https://www.garden-lang.org/
Today I learnt that Racket *intentionally* doesn't have a traditional REPL workflow. The authors were concerned about students not understanding the state between the current session and the code on disk.
(Arguably Jupyter has some of these features now.)
https://blog.racket-lang.org/2009/03/the-drscheme-repl-isnt-the-one-in-emacs.html
I'm experimenting with jj this weekend. It seems pretty nice so far, but the mental model is pretty different from git.
For example, there's no `checkout` command. You do `jj new ABC` to switch to a commit, which creates a new empty commit on top of ABC.