To view parent comment, click here.
To read all comments associated with this story, please click here.
Scripting is about iterative development, fast iterative development. Change, run/test, done.
I think Linus Torvalds said it best in his Google tech talk about Git:
When something is fast, you use it differently.
If it takes less time to build, thus it is cheaper.
You don't have to use cheap programmers/cheap labor to do it. Actually I would recommend not do so.
When making larger things, you want some programmers to take time to investigate and think before they start. You want to make some proper choices about structurale/architecture. Lay a good foundation and stick to that.
Where should PowerShell be used ? System administration ?
When something isn't working a busy sysadmin just wants to do a quick fix to a script to keep the systems running. And probably come up with a proper solution later.
First priority: keep systems running.
The perfect example of an environment that asks for for quick iterative development ?
Take any server with Microsoft software installed, it installs lots of modules.
That is when it gets slow, by default it loads all the modules installed.
One of the changes with v3 is that modules are now loaded on-demand. You can enumerate cmdlets for all available modules without actually loading the module into the session. They are only loaded when one of the cmdlets they contain is called.
http://technet.microsoft.com/en-us/library/hh857339#BKMK_AutoLoad





Member since:
2007-09-22
Try installing some PowerShell modules.
Take any server with Microsoft software installed, it installs lots of modules.
That is when it gets slow, by default it loads all the modules installed.