miniblog.

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

It's weird that GitHub shows time since the last commit, but not time since the first commit. It's a nice way of seeing how mature a project is.

It's really satisfying to use a profiler for the first time on a project. I always find a big performance win with only a small code change. It's never the code that I expected to be slow, however!