Using UnrealIRCd with Anope 1.7.9 (Development)

[Keith]

I had a services question. Isn't running services that are in "Development" just as risky as running a public beta of some software or an RC version? Not to say that Anope does not do a fine job I'm sure with there software, but isn't there a good chance that Anope could somehow crash? I mean despite all there commands and the cor becoming modularized, isn't there a chance that running development versions of software could lead to a security exploite etc?
I do know for example of some networks who run versions of services from Source fordge that are in partickular in development or unstable brantch releases, but I have never really seen anope crash (well on Winblows? Plenty of times.) I do believe that software programmers have a right as to if they want to support Windows binarys of there software, but then again, look at how nice Linux handels UnrealIRCd for that matter, and services. Why, unlike Windows, once you link services, etc,
you can't really tell that you have linked anything.
If I ran services under Windows, I'd be getting this very annoying DOS window, which only would be another annoying RAM consuming window showing up on my screen, and since I use screen readers to help me access computers under Linux/Windows, I find that using linux is what I'd prefer since Windows is *not* a server platform period. I mean, look at the services Microsoft shuvs at us, I've got about 80 or more, perhaps, running right on this SP2 XP professional box, and I really hate that. Now for a scary, scary, thought; Linux being like Microsoft Windows? Picture what would happen if Linux did this? (shutters.) You're system performance at some point regardless of ram would begin to suck if Linux by default ran over 39 services by default, on top of all the other services you wanted to editionally run...
I mean, how would you expect to avoid crashes? I've had too few crashes, i.e. Loading one moduel into Anope or something causes Services.exe to crash, and generate an error report to Microsoft.. LOL. Look at Linux on the other hand: You don't have this type of problem under *Nix environments. And this is another reason why I use Linux for most of my work, and Windows for not much more then posting to foarms here, and ocassional email/web browsing/voice chatting/msn messenger, etc, but that's about where I draw the line for Windows. , oh and reading documentation when I'm too lazy to use a Linux text editor.
Thanks, Keith.
Note: I am using Anope version 1.7.9 with UnrealIRCd 3.2.3 on my *Nix box and everything seems to be purring along nicely.

[Stealth]

It is true that Anope Dev might crash or have some crazy exploit, but when they release a Dev it is usually fairly stable. I have not had an Anope Dev crash yet myself... *knock on wood*

[heinz]

This can be said of any program released, not just Anope. There may be some really obscure, but potentially leathal security risk, or bug, in any piece of software around. In the past, it's true that some development versions of Anope have been released, with some very nasty issues, but these were dealt with quickly.

On the hand of Windows vs. *nix, this argument is very old, and there is no right or wrong answer. Each OS is designed for a specific purpose, some do it better than others, whilst some are used because the user has no alternative.

When you talk about 'services.exe' (which hasn't existed since 1.7.3 ) and loading a module, I have /never/ heard of this bug. In 1.7.9, with the modularised core, there are zero issues with loading any kind of module, whether it be protocol, core or other. If you do have problems, by all means, let us know, and we might actually be able to do something.

As for the rest of your post, I wasn't able to understand the point you were making. If you have any particular issues with Anope, i'm all ears.