Morgan and I are starting to loosely plan a "digital humanities" course using Racket & Scribble.
@willghatch Getting comfortable with DrRacket and Racket through the picture tutorial; writing an example document in Scribble; writing tools for yourself for document authoring (eg formatting images in your document, generating graphs based on data procedurally, etc)
if a longer course, it would also cover an intro to the command line and how to use version control to keep track of your writing history
@willghatch One reason it would be focused on scribble is I'm a strong believer in quickly getting people to the point where they can do something where they can see real output in a way they can imagine being useful.
Lots of academics author lots of things; focusing on Scribble helps bridge that gap faster is my hypothesis.
Actually being able to quickly teach people enough to be able to make useful things (and without having to learn several different languages) is part of the reason I made [rash](https://github.com/willghatch/racket-rash). You could use it in your shell portion, and students could still leverage their familiar Racket functions inside shell code.
@cwebber Yeah, scsh is cool. I when making Rash and its underlying libraries I tried to keep a lot of the good parts of scsh, but adding new things like a good command-line friendly syntax.
As to safety, I wouldn't recommend embedding shell stuff inside serious programs. But I have often wanted my shell scripts to grow up -- add real data structures, load libraries, etc. So maybe instead of thinking of shell adding unsafety to Racket, think of Racket adding power and safety to shell.