Me personally passing out precompiled binaries is asking for trouble. I won't do it, and I doubt anyone else on the dev team would as well.
I could get accused of passing viruses, trojans, malicious code, etc. Who knows if someone out there is out to get me? No need to make myself vulnerable! It doesn't even have to be malicious code - the code an official dev has is different than the code on SF CVS, which means we would end up with arbitrary versions of the code floating around. It's a headache to support code where the version is arbitrary or unknown - much less when no two people have the same version.
Furthermore, the binaries on my machine have lots of debug code that I use for myself - code that you would not get by compiling your own. I've done it in the past, and the next day I would see threads asking why they are seeing such-and-such message, when it's really just my own debug code. Now I have to support my own temporary debug code?
Then, once that has been cleared up, I inevitably have to spend the next 4 days teaching that person how to set up a server and holding hands for every little movement. It's just the way things work - you get a binary from somebody and you can't figure out how to get it to work - who else would you ask for help? That's 4 days that could otherwise be spent writing eqemu code!
At this point, if you aren't able to compile your own, it's likely you won't have a seamless experience setting up your server. Therefore, I am not handing out binaries until an official release.
|
Threaded Mode
