Scripting, and different strategies

In the past, scripting has been a real strength of Microsoft technologies. I’ve seen some very capable solutions built with visual basic, and as new generations of technologies emerged, I expected Microsoft to provide more robust solutions.
Scripting is important, because it lets you come up with flexible solutions. Most of the arguments which are against scripting for large scale development focus on weak type checking, and performance. However, scripting has one very important advantage: when you build a core set of functionality which covers the basic requirements of a domain, scripting gives you the ability to provide this functionality to others who might have less information about the domain.

When you can make junior developers create a solution for you, you have a cost advantage. Using scripting gives you the ability to come up with domain specific languages, which are the way of the future in my opinion. Scripting also has some technical advantages, which lets you work in a loosely coupled environment. You can dynamically update scripts, which has many benefits compared to usual code, compile and deploy scenario. I might be a little bit exaggerating, but recent approaches like Ruby on Rails are close to scripting solutions, even though dynamic languages is the correct definition for them.

The problem is while Sun seems to be embracing this idea, Microsoft seems to be getting away from it. In the past Microsoft’s scripting solutions provided very nice features to pass native objects back and forward between compiled domain and scripting domain. After 6 years, scripting seems to be going into a certain subdomain in Microsoft world, which is management. Monad seems to be the only active scripting effort of Microsoft, and it does not seem to be positioned like the good old scripting host, which you could drop onto a form (both for vb and windows forms) and use.

There are products/technologies like VSA which looked like the new scripting solution from Microsoft for a while, but they are dead now. So Microsoft, what are you going to do with this? WPF and XAML has great potential for scripting support, but it appears to be only supported in Silverlight! Why on earth do you provide dynamic language support to Silverlight and do not build it into WPF? Maybe they will, but the overall direction of scripting for Microsoft is very vague at the moment, and this creates a serious disadvantage for me. Let’s just hope it will get better (maybe in the form of dynamic language support) when 2008 is released.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s