The Soul of Barb's New Machine 1144

comes in

Hold the phone! You guys are talking about coding technique tradeoffs. I was talking about the tradeoffs made at the "what are we going to implement next?" time of a project. For instance, BSD developers made a conscious or unconscious decision to concentrate on comm thruput. That's why that flavor of Unix was better at it than System V. System V's guys, at some point in time, did the same with disk thruput. I suspect that the reasons had more to do with who was using the code. A university tends to need higher comm thruput than disk and a data intensive biz needs disk over comm.

This is the kind of tradeoffs I'm talking about that can never make it to comments in the source code because the decision and reasons have been made man-years before the project work gets around to coding. it something, problem problem deep dark often

Well, for this kind of stuff, the safest place to have it documented is in the code. An even safer approach is to have the TTY extrude an axe in chopping mode if the programmer tried edit it. :-).

BAH

Subtract a hundred and four for e-mail.