task VS script

Interesting. I do something similar with my task https://github.com/kardianos/task package, which is in tern loosely based off of another package from 10-15 years ago.

Yeah, another way to do this, rather then chaining methods, is to provide a consistent interface that get called. I've seen this done a few ways, here is mine: https://github.com/kardianos/task ; don't necessarily recommend it, though I may see if generics add anything to it.

I use Go. You can run scripts with go run directly, and this package makes shell tasks easy: https://github.com/bitfield/script

If you're not deeply familiar with Go there is one detail missing from this post (though it's in the script README) - what a complete program looks like. Here's the example from https://github.com/bitfield/script#a-realistic-use-case

    package main

Imho also worth mentioning: https://github.com/bitfield/script

I would say bitfield/script is the closest thing to plumbum. You should check out this article written by the author.

There are lua and Go-script options. My impression is that a few are well accepted but perhaps just a little less widely used than the first two. I cannot speak from personal experience on them. Shopify has a Lua 5.2 port: https://github.com/Shopify/go-lua and I know https://github.com/bitfield/script is one of the Go-like scripting languages, but I think it's more for a shell script replacement than embedding.

Parallel to my other comment, u/Akirapearl, if you find yourself getting annoyed at Go’s system-language focus, you might find John’s “script” Go library useful: https://github.com/bitfield/script

It took me a while to find the link to the library "script" and it's repo - https://github.com/bitfield/script