Here's an article about «Visual Studio for Applications». It's a generic environment you can use in your program to make it scriptable using any language supported by VSA (e.g. VB.NET, JS.NET).
The article starts out marvelling at how amazing DOOM was, and especially because an MS-DOS program can run on this week's build of WinNT[1]. One of the problems the author highlights is that the scripting framework for the various releases of DOOM changed with each release, including the «scripting language» needed to tweak the engine. Oh, and it was interpreted; we all know how horriby bad it is to have an interpreted language these days. Only slackers avoid the trivial amount of work to compile a «scripting language» down to native code, after all...
So, what example does this article use to demonstrate the benefits of VSA? A little application that controls four independant clocks with second hands. We all know how performance critical a clock is, and how it's completely unfathomable to get enough performance out of a «scripting language» on a modern 1+ GHz system to update four second hands once per second...
There is something of value here. I'm sure of it. But I'm not sure what it is though.
[1] The intro was written like it had to fill a few obligatory story elements.
