Mostly it's where using the shell would be painful. Do you have other specific examples?
This is the same reason why I dislike, for example, seeing the documentation of a library showing how to perform actions X, Y, and Z, but a footnote says "by the way, there is no error checking in this example". Well then, why use this code as an example?
Anyway, sorry for the rant. ShutIt does seem interesting :)
Actually, I have similar problems when teaching - I'm writing a git course at the moment, and it's hard to illustrate concepts in a realistic way without hopelessly artificial repos.
https://github.com/ianmiell/shutit-home-server/blob/master/S...
so I can port to Centos from Ubuntu pretty easily.
PS That's an example of a ShutItFile, which is still a WIP.
For example, from the example on the home page:
Awesome and very powerful abstraction! Vs the next lines... Why not just: There are a few other examples where I was wondering how you decided to do some operations in ShutIt vs delegating to shell. In fact, some entire examples look simpler to me in shell that you could just send. Does using the ShutIt native commands make things more testable?