I didn't say I had anything against dlls, I just prefer not to use them when you don't need them. mSL is a very unique and fun language, I also like to test how far it can be pushed, I've done all kinds of stressful tests like 3D rendering for example just to see what mSL can do and I like sticking purely in the limitations of the scripting engine itself rather than breaking out of its environment and using some com object or dll to do the dirty work.
I love mIRC for what it is, and try to be as creative as possible within the language itself, if I need a dll to do it than I probably don't need to do what i'm doing with mIRC. mIRC is a fun toy and not my primary choice of a coding language, its definately NOT the best tool for all projects but it is a break from the usual and a hobby I quite enjoy.
Sticking to these boundaries also helps me come up with what I feel would be useful feature suggestions. DLL's are frowned upon on a lot of mIRC fan based sites for general addons you'd like to release to the public. Users are also cautious about DLLs and tend to not want to use them without the source, and chose not to even with the source because they themselves don't have the compiler to generate the dll and don't want to chance the "pre-compiled" one included in the package. The source may be legit but the provided one might also be malicious. Some people may also use alternate compilers such as borland, microsoft visual studio, mingw, etc.. theres no garuntee that the structure of a dll written for visual studio may compile in their favorite of borland, so now you have issues of porting from one to the other.
I myself use windows in a virtual environment (where it belongs) and keep a backup of my virtual drive incase of virii or data corruption, etc... for anyone who doesn't use windows as a virtual machine, I'd call you stupid if you blindingly trusted a pre-compiled dll included with the supposed "source" as you're just asking for trouble.
