If that is true then what is the advantage of VB to other language's.
Well it's the easiest and quickest way to code ASP pages for a start, and as the default server-side language for IIS, probably the most appropriate language.
Making dialogs without an Visual tool is a trivial task, albeit tedious, and isn't the hallmark of an excellent scripter. Anyone can do it. Infact that's how most of started off.
To each their own. However I cannot understand why I should be expected to use someone elses work to create my own work. Even in Microsoft Development Environment, while you can 'draw' a dialogue, you still code the functions manually in an editor.
My crack about Notepad being l337 was sarcastic. I don't consider myself to be a gun coder, I just enjoy knowing that I can do something without having to either:
1. Prove it to others for the sake of letting them know I can do it.
2. Use someone elses scripting or tool to achieve it.
The only difference is that it's more time consuming. And this isn't one of those matter of prefernce issues, anyone who spends an hour doing what could be done in 10 minutes with an Dialog editor is a fool.
I've made a dialogue with 2300 lines of scripting - it's called a channel central. Don't expect to emulate that in a dialogue maker. I would in an instant question the ability of a dialogue maker to achieve what I did manually in that respect. The feature list is simply too rich to consider anything else.
I would disagree with the idea that to be serious about scripting you have to use a dialog editor but thats no reason to swing to the other extreme of foolishness.
I didn't "swing to" anything. That is my point. I use the mIRC editor to make dialogues and won't be changing that.
Final points: Isn't it possible that a dialogue maker could still produce bugs? If so wouldn't that require some stuffing around to sort out? As for VB, well, I code that manually in Notepad because the functions I require for my website do not require the need to do the job in MS Dev.
