> Just try these in Bash or PowerShell! > select fullpath from files where fullpath like '%sublime%' and fullpath like '%settings%' and fullpath not like '%backup%';

This isn't a very good example, because it's trivial to do in bash:

    locate sublime | grep settings | grep -v backup

(Replace `locate sublime` with `find / | grep sublime` if locate's results are too old.)

> select fullpath, bytes from files order by bytes desc limit 5;

This is better. Here it is in bash:

     find / -type f -exec stat -c '%s %n' {} \; | sort -nr | head -n 5

Cherry picking another one that stood out to me.

> select writeln('/Users/SJohnson/dictionary2.txt', data) from fileslines where fullpath = '/Users/SJohnson/dictionary.txt' order by data;

    cd /Users/SJohnson/; sort dictionary.txt > dictionary2.txt

Some of the rest of the examples are trivial in bash, and others look potentially useful. Of course they are trying to demonstrate its capabilities so the examples are contrived. I can see how this would be useful for someone who doesn't know the command-line, but as someone who is proficient in both SQL is pretty verbose.

In the real world I'd switch to a scripting language for some of the more complex cases, since they'd be rare.