|
True, but that seems to be the route that most muds take - sharing with other muds on a unix-style platform. And remember, this is supposed to be a public codebase, aimed at a wide audience of potential mud owners.
The problem with a server crash is that you need someone there to reboot it. Now I can tell you that my windows machine crashes on a fairly frequent basis, while I used a linux box ran for years without a crash. Mud crashes are annoying enough as it is, but at least the mud usually comes back up within a few seconds - a system crash, which won't come back up until someone reminds the hosting owner to do a reboot, is going to be downright annoying.
Then there's the whole host of security-related issues...
Windows does have things going for it, and would be good for the client-side development, but IMO it makes a poor choice for the primary OS of a publically available codebase.
Indeed, that's another major problem.
|