> student. Would it be possible or desirable to make any of the > suckless tools/programs to suck even less by writing them to use > netcat or inetd and removing all network-specific code? Do one thing > and do it well? Is Plan 9 the logical extreme of this practice?
Depend. This is always the answer. There are cases where the network code is the central part of the program, like for example identd, but there are other cases where the best option is to create a textual protocol, and use nc/inetd, like the case of ftp/http. Of course, if you need high performance (that is not the common), you can not rely in nc/inetd solutions, but you can begin with somethig simple and create the complex solution only when you need it. This is also part of the Unix philosophy. Regards,
