Are VBScript and WSH Script dying slowly? 1

[cowcool]

Hello All,

Are VBScript and WSH Script dying slowly?. What are the future of both?

How about MSH?. Should we prepare to switch to it?

 

[EBGreen]

I think that the use of the WSH will taper off, but I think that too much has already been written against it to allow it to die off quickly. I think whether or not Monad will allow direct use of non-ActiveX components will have a direct bearing on how quickly it will be adopted.

Just my $2.0E-2

[blue]"Well, once again my friend, we find that science is a two headed beast. One head is nice, it gives us aspirin and other modern conveniences,...but the other head of science is BAD! Oh, beware the other head of science, Arthur; it bites!!" - The Tick[/blue]

 

[EBGreen]

Is this the blog that prompted this question?

http://blogs.msdn.com/ericlippert/archive/2004/04/09/110508.aspx?Pending=true

[blue]"Well, once again my friend, we find that science is a two headed beast. One head is nice, it gives us aspirin and other modern conveniences,...but the other head of science is BAD! Oh, beware the other head of science, Arthur; it bites!!" - The Tick[/blue]

 

[dilettante]

MSH/Monad isn't even on my radar scope yet. It looked interesting when it was announced, but it is probably years from being included in any shipping product, and more years before existing platforms (Win2K, WinXP Pro, Win2003 Server) are displaced by the next great thing.

I'm not even convinced Longhorn will directly result in a server platform, though MSH for Win2003 Server seems likely as an add-in.

Have you looked at MSH yet though? Sure doesn't strike me as admin-friendly. It offers nothing to speak of for other script users, so don't turn to them for help. So where are you going to get all of the "MSH scripts" for you to "drive" from the shell? Canned ones from Microsoft?


I suppose the world "smells like" WSH to a box admin sort of guy. But the saving grace for VBScript is that it's hosted in so many containers: IE, ASP Classic, Office Suite products, 3rd party software... it'll be hard to kill off VBScript.

As for "slowly dying" I can only agree. But while not perfect, it has most of what you need in a scripting language already. Most of its real power comes from the host it's embedded in and the ActiveX objects it can manipulate. My guess is that it will be a few more years before things needed by an administrator will only be made available through managed-code (.Net) components.

In the meantime there are hacks and 3rd party ActiveX components and component-suites to help make up for shortcomings (binary file I/O, etc.).


Even if VBScript and WSH died off completely, almost any truly "vital" WSH script can be converted to VB6 with little trouble and compiled there.

 

[rcraig12]

Im not sure if I agree with VBScript dying out. BASIC has been the language of programming for beginners, for ever.

I think VBScript is yet to fully develope and the new emerging technologies will, as with all MS products be a transition/add-on.

WSH is an example of an add-on. No matter how you look at it. It provides access to WMI, ADSI, etc and thats its power. VBScript is still required to drive it.

I can only assume at this stage. MSH will be no different in methodology. If MS brings out an alien product .. Well the plane truth of the matter is as with all their products.

The customer is the driving force and MS capitalises on providing what we are looking for in next step. You know, "If it did this it would be reallly!, cool.".

Fair to say by the time MSH hits us. We will all be gagging to use it. Business is the driving force and business trusts\fears the Microsoft product line.

So buckle up and engoy

cya

 

[dilettante]

For those so motivated, you can get Monad as described here:

Installing Monad on XP or Win2k3