View Full Version : My 2 cents worth on closed thread "Scripting and ASP"

07-15-2002, 03:01 AM
Here's the original thread:

I wasn't a member when this thread was closed, but here's my thoughts...

Also new to ASP programming my question is why use VBScript at all? It is possible to write server side Javascript - Jscript is MS's version of standard JS. Additionally Netscape's server side scripting does not support VBScript.

I'm asking from a code maintenance perspective. Why support two languages when you don't have to?

When I asked one of our programmers in our shop, he said 'well, it's just another language' i.e. no big deal to learn and use. I fully expect an answer like that from a programmer (and I count myself among that lot). More fun stuff to learn and tinker with. More syntax to learn, subtle differences to keep track of - and when I learn it all, boy will I impress the hell out of myself!!

Like any other programmer I like learning and using other languages, but from a real practical standpoint you have to ask yourself, for a given project why do this? That's same programmer's answer was 'because all the code samples we got, and the books, all do it. "

If we take this logic and apply it to say a C project we could write code in C, C++, COBOL, FORTRAN, etc. and compile and link it all together. Now that sounds like nonsense and I suggest it is also nonsense to mix VBScript and Javascript. Of course Microsoft supports doing it that way and I guess that enough, whether we like it or not.

Anyway for every language we use in our coding show we have to train folks, buy software tools, books, etc. etc. It causes hardware and manpower logistical problems.

It takes time to become a real expert in any language, even a mere scripting language. We end up was a shop full of programmers who are jacks of all trades, and masters of none. And personally I think that's a problem where I work. It seems like everytime a new project comes up we are paying a price for the new guy on the project to get up to speed on a language s/he isn't familiar with - and around we we are all self taught out of necessity.

07-15-2002, 07:19 AM
Originally posted by Dave Clark
What about the Visual Basic programmer who decides to start coding a web application? Why should they code ASP/JScript? For them, ASP/VBScript makes more sense because around 80%, or more, of Visual Basic can be applied directly to the use of VBScript. Also, for them, the use of client-side VBScript makes more sense, too. Right? :)

Right on Dave. :)

Thats is exactly what applies to me.

Plus if you know VB/VBScript you can easily learn VBA which MS Office and a few other programs make use of.

07-15-2002, 02:17 PM
I'm not saying JS is better than VBS so use JS. I'm saying why use multiple languages when you don't have to?

If going pure VBS makes sense for your environment, then fine. If you can say "all our intranet customers us I.E. then why bother with javascript on the client side?

To aruge that different implementations of Javascript are different is true for any language (VB is not the same as VBS is not the same as VBA - close, but not the same). Also, every compiler for a given language is different, even if they are trying to implement the same features.

So why compound the above problem by unnecessarily using multiple languages?