* 1. When forking OS (Operating System) processes, which are your main goals?

* 2. When you fork processes to execute commands, in which OS do you normally do it?

  Never Ocassionally Sometimes Frequently Always
Unix-like
OSX
Windows

* 3. How frequently do you rely on shell (.e.g /bin/sh -c 'ls')  as the command to be executed?

* 4. When you rely on shell, which are the main reasons for doing so instead of executing the commands directly?

* 5. How frequently would you like to pipe commands from Smalltalk side rather than delegating them to bash? That is: instead of invoking the bash command and doing "/bin/sh -c 'ls | grep test' ", you invoke a command for 'ls' and pipe it (from the image side) to another command ('grep test').

* 6. Could you justify the previous answer? Do you see special advantages or disadvantages with the mentioned approach?

* 7. How frequently do you use "synchronous process execution"? Let's say you have forked a process to invoke certain command from the OS that takes some time. Assume the image is not locked during the time of the command execution (the image can continue working). The question is: how frequently your code (at the image side) needs to either wait until the child process has finished or until you have read all the available results from standard streams, in order to continue it's code execution?

* 8. How do you normally read from the standard streams (stdout, stdin) of the child process?

* 9. What things you *don't* like about current implementations (OSProcess and others)?

* 10. I am interested in hearing about your experience with OSProcess. Feel free to share this information here or via email. If you want, you can also include your name so that we can discuss privately.

T