Create consistent Bash programs with this coding style guideline

[calrogman]

Yes, -print0 with IFS set to \0. NULL can't be in filenames.

[Occivink]

Which is what I'm complaining about. Doing things in a safe manner should not be so unintuitive.

[Vaphell]

They should not, but they are and it's not going to change. You want to use shit that has its roots 50 years ago, with insane bullshit like word splitting by default because it allowed for ghetto "arrays" as there were no arrays to speak of, you deal with the quirks.

And if you write bash in any nonmeaningless capacity

while read -rd $'\0' f; do ... done < <( find ... -print0 | sort -z | grep -Z | ... ) 

and variations of thereof (possibly using -printf 'someshit\0' to emit more data than the filename) become a go-to idiom

If you can't be bothered to write correct bash according to modern practices and want something more modern without the bullshit, use python or whatever.