No such example; after all, you can spawn a shell subprocess in any of those.<p>There&#x27;s just certain types of tasks where you can more clearly express your intent in a shell script. If, for example, you need to spawn a ton of subprocesses, you can do that in any scripting language, but shell is designed from the ground up to launch subprocesses — it&#x27;s most basic purpose is to launch programs.<p>And so while I can&#x27;t give an example of something that can <i>only</i> be done in a shell script, here&#x27;s a shell script that I wrote a few weeks ago that would have been a pain in the neck to express in any other language:<p><pre><code>    #!&#x2F;bin&#x2F;sh
    cd &quot;$(dirname &quot;$0&quot;)&quot;
    for test in *.in; do
        test=&quot;$(basename &quot;$test&quot; .in)&quot;
        infile=&quot;$test.in&quot;
        outfile=&quot;$test.out&quot;
        output=&quot;$(.&#x2F;whofrom &quot;$infile&quot; 2&gt;&amp;1)&quot;
        expected=&quot;$(cat &quot;$outfile&quot;)&quot;
        if [ &quot;$output&quot; != &quot;$expected&quot; ]; then
                echo &quot;Failed test $test&quot;
                echo &quot;Expected: $expected&quot;
                echo &quot;Actual:   $output&quot;
                echo
        fi
        if ! valgrind --error-exitcode=1 --leak-check=full .&#x2F;whofrom &quot;$infile&quot; 2&gt;&#x2F;dev&#x2F;null &gt;&#x2F;dev&#x2F;null; then
                echo &quot;Failed test $test&quot;
                valgrind -q --leak-check=full .&#x2F;whofrom &quot;$infile&quot;
                echo
        fi
    done</code></pre>