beacuse VS is only made for programing and nothing more
mirc is CLIENT that fotunately can be altered with scripting
mIRC is an
IRC client, it's funny how you missed the most important word. It is *made* for IRC and nothing more. The fact that people use mIRC as mp3 players is not the main intention of the author- mIRC is still an
IRC client; that's why IRC is prominently displayed in the name.
By the way, Visual Studio can
also be extended by plugins just like mIRC can.
So by the same token, people could extend Visual Studio to be an mp3 player just like mIRC. But as you said, such an extension would NOT make Visual Studio an mp3 player, because it is and has always been a programming tool and nothing more. Your problem is that you fail to make this same exact logical connection with mIRC.
To be more a little explicit about my point, mIRC can *also* be extended into an mp3 player, but to quote myself: "such an extension would NOT make
Visual Studio mIRC an mp3 player, because it is and has always been
a programming tool an IRC client and nothing more."
And I think the root of this oversight has to do with that little intentional mistake you made at the top of your post by leaving out the word "IRC" when describing mIRC. If you refuse to acknowledge that mIRC is an
IRC client and claim that it is just "a client" (a client of
what, by the way?) then you will fail to see the obvious truth lying behind this program:
Khaled isn't creating mIRC to be your programming environment, he is creating it to be an IRC client. Instead, you're using mIRC as a programming environment.. clearly this is true, because an mp3 player has nothing to do with IRC.
Now, it's probably easy for you to misinterpret what I just said and conclude that I think all extension of mIRC beyond the scope of IRC is bad... I don't. However, you must understand that you're running mIRC in an edge case scenario here-- in a situation it was never intended to be used as.. kind of like
writing PacMan in Excel. It may be cool, fun, and useful to many, but it's not the purpose of this program.
All that said-- no one stops you from writing scripts, and Khaled put plenty of time into the scripting engine to give you all of this power. And he did this specifically so that you could use it-- use it to extend mIRC how you see fit. So when you're complaining how mIRC doesn't have your favourite mp3 player script built in,
or even flood/clone/massdeop/spam/etc. protection.. well, you just answered your own question. It's not builtin because it's available as a script. This is how mIRC works. It's how mIRC
is functional. The functionality lies in the ability to script it. How you missed that simple fact is beyond me, but anyhow.. listing a bunch of scripts actually helps to prove how functional and complete mIRC
*is*, rather than not.
So you may say that mIRC is not intuitive because it requires you to script your functionality...
That is a fair argument.
To that I say:
If you don't like mIRC's design choices, feel free to use another program. No one forced you to use mIRC. There are IRC clients that give you a baby UI with some (not all) of the features you described. Go use that. mIRC will still remain highly useful to a ton of people, and pleasing every single computer user was never the intention of this program, AFAIK.
What I'm trying to say is: It's really pointless to say that a well established program with a huge community should all of a sudden start catering to a group of individuals it never intended to cater to-- because that is not the purpose of the program. The users that this program does not cater to probably have an array of program choices that *do* cater to their needs. A good author focuses his efforts on his community first, and new users second- not the other way around.
I think almost every registered user on this forum is happy with the way things are now, and wouldn't want mIRC to change for
someone else.