|
An amusing example erdos, but hardly a scenario with "individual modules that can be plugged in".
The biggest problem is actually getting started, as described in Tyche's example - but once you've got that sorted out, each person can do their own thing. And as long as they follow the agreed upon design approach, every contribution is potentially useful.
Coder #56: Here's my server module, what do you think?
Coder #104: I decided to do it this way instead.
Coder #37: Here's my multithreaded solution!
Coder #79: I don't want a mud, I just want to play on my own - he's my single-player solution.
Result: You've now got three different server modules that other developers can choose from, as well as a single-player module that could be plugged in and used by someone who just wanted to do some single-player gaming.
Now repeat the process for additional modules. Some of the later ones will no doubt have dependancies, being based upon other modules, but it would still give a great deal more flexibility than is currently available.
|