> 3. Is there enough code to fill more than one screen? Out of the shell I go. Completely disagree. Just parsing a command-line takes a screen's worth of lines

> 3. Is there enough code to fill more than one screen? Out of the shell I go. Completely disagree. Just parsing a command-line takes a screen's worth of lines. Hell, just the usage info message for a script can take that much. > 4. Is this going to be something that needs robust error handling and that will be used frequently outside of me? Out of the shell. Disagree even more strongly. You're saying never to write shell scripts for use by many people. Actually, shell scripts make up a lot of a typical systems' /usr/bin and /usr/sbin - and that is fine and proper.