Wraith 2.0 development beginning

Wraith 2 will be written from scratch. No base will be used like with 1.x. Eggdrop components will not be used. Original code/components from Wraith 1.x will on the other hand, be used. This decision was brought about for many reasons.

• Wraith's eggdrop base makes it difficult to expand with new code/ideas. Code must be gradually migrated to new protocols, which is very tiresome.
• Eggdrop is bloated, ugly, and slow.
• When I first began working on wraith, I was a novice at programming; now I am an expert.
• Wraith 2 will use  Unit testing from the start, which means much less bugs.

For wraith 2, I need to write up my own general library to handle such things as sockets, adns, files, threads, children processes, etc... This library will be relased under the  GPL (with the sole exception that I may use it privately). Development on this library will be open to whomever wishes to help, but no credit for wraith will be given.

All wraith specific code will remain private.

I may investigate adding scripting/module support to wraith2 to both handle user requests which seem to be too much bloat for the average user, and to help inspire new ideas.