ok since uve addressed this in a 2 part deal ill try to cover it all in one place. now uve stated that it is your beleif that the reason mirc doesnt support stuff is because it wasnt coded for it beforehand, and uve used the example of unicode support, well im sorry to shoot your idea down yet again on that but, khaled himself stated he will infact be adding this to mirc via UTF-8, im not making this up it is a fact khaled himself stated it will be added at some point in the near future. now with that said, whats to stop khaled from adding anything else? answer is nothing. now lets try to cover your second post.
DLL support, ok yes u may have a point asthetic changes where mostly aded to mirc before dll support, ok then how many times has khaled changed dialogs look and appearance since dll support? ive noticed it 3 times in the recent past. and just in 6.1 versions .txt hes added undated jpg support(Asthetics). so again the dll idea isnt really true, infact isnt almost all of the additions and fixes to mirc in someway related to mirc appearance or operation, and really as mirc was back in version 3 it had all the functionality and visual appearance it really need just to be a chat client? yet its still developed, ironic isnt it. ill leave u with this, if mirc does not grow as a client then it will surely die, so additions and suggestions from its users should be something it atleast tries to implement, this is the best way i can think of to make the best of both worlds , where users want emoticons and others dont, its then turned scriptable and even highly configurable, basically what mirc has always aimed to be. again how am i wrong?
