Hey Richard!
There are a few differences between Interlace and a bash loop — most importantly, Interlace will multithread the tasks instead of running them one after another, making it much faster. Interlace also allows you to define a list of command templates in a file and run all of them, so rather than having a giant bash file with a series of loops, you can just specify your go-to commands in a single file. That way, on every engagement you can simply update your “targets.txt” file and run a single Interlace command to kick off all of your standard scans.

Of course, I’m also a big fan of bash. As many have pointed out, you could achieve similar results by using a threading CLI tool such as GNU parallel and a bash script.. But why would you, when Interlace has already been written to do it for you?

Hope that clears things up!