Rigid file name schemes and interoperability

Some programs require that the name of the passed file has a specific scheme. For example, just now I want to start programX and it won't work, if config file has no proper extension. There are better or worse reasons to do that. But the cons include, at a minimum, reduced interoperability. For example, 'process substitution' is a convenient way to pass file-like objects constructed on the fly…