why would you want to use sh for your own userspace scripts? Do you have a computer from the 20th century that shaving off that 100k of RAM matters? Bash offers tons of nifty stuff that is not accessible in sh (dash)Yeah, I was using sh not bash. I've got it working now so I'll stick with it, what I've got works with both bash and sh. I guess that line means something.
You are gimping yourself for no reason. If you have cool features within your arms reach, use them, don't reinvent the wheel with hackish workarounds for the sake of it. These features were in fact implemented to alleviate many of such basic problems like this one.
bash <( cmd ) that means 'capture the cmd output and make a fake file of it' is incredibly powerful, it works everywhere you would use files as input. some_command file? have some_command <( cmd ) instead. You don't pollute your hdd with temporary dump files and can cut to the chase.