I'm not sure what you mean by "VBScript with JavaScript" -mixing both on a single page?-, but VBScript is limited to one particular browser on one particular operating system, so you'd be shutting out a lot of users from your application.
What benefit do you see in using a mix of VBS and JS over just using JS?
Originally posted by Ulf Dittmer: Welcome to JavaRanch.
I'm not sure what you mean by "VBScript with JavaScript" -mixing both on a single page?-, but VBScript is limited to one particular browser on one particular operating system, so you'd be shutting out a lot of users from your application.
What benefit do you see in using a mix of VBS and JS over just using JS?
Dharmendra Sable
Greenhorn
Joined: May 30, 2006
Posts: 13
posted
0
Thanks for your information. Yes I was talking about the mixing the scripts. This had come up during one change from OCX dev team that they wanted use "CreateObject() " method . I am not sure whats the advantage of it.
Ulf Dittmer
Marshal
Joined: Mar 22, 2005
Posts: 35439
9
posted
0
So they want to use native code. That would only work on IE on Windows anyway, so since nobody else is supported, there's no harm in using VBS. But in that case the question becomes: Why use JS at all? Keeping the number of languages used to a minimum is a good thing.
I'm intrigued that an IE/Windows-only web app is developed using JSP; usually Windows-only shops prefer ASP.
Why use JS at all? Keeping the number of languages used to a minimum is a good thing.
Very good advice. I worked on a number of Windows DNA apps in days gone by which used VBScript for the ASP and also had extensive JavaScript in the client. The amount of bugs we got because developers were having to frequently shift from one language and its keywords/control structures/minor vagueries to another was huge. Even more so since both languages are interpreted, so application-crashing bugs could lie undiscovered for months till someone hit the right number of conditions to trigger them. Horrible, and best avoided.
0
