Good old APL, a write once language. I go back a couple years before that yooakim. :)
On the Mainframe I was introduced to scripting with CLIST
One of the reasons I was drawn to Monad/PowerShell was it's inspiration from AS/400 and DEC DCL.
The culture back then, everything was written in IBM ASSEMBLER Language (BAL) . Registers, OPCodes etc.
I found using a scripting language to sketch out ideas got the software in front of clients quicker and helped everyone involved make quicker decisions about the shape of the problem.
Then, we could move forward and keep the pieces that just worked (in script) and bake others into BAL for performance or reuse in larger solutions.
Like others have mentioned. There are several aspects to consider when choosing an approach to building software.
I'm thinking PowerShell raises the possibilities and leans more to an "AND" compared "Either/Or" choice point.
Drawing from the gaming community. Lua
is very successful in it's application in the World of Warcraft.
A scripting glue for the hardened C++ components that make up the game.
We also see this from Microsoft, they are delivering new PowerShell cmdlets over their existing products. In PowerShell v1 we saw this done in Microsoft Exchange, plus a GUI layered on top of PowerShell.
I believe to become more agile developers, we need to be exposed to this and begin to embrace it.