Around 2005, PowerShell was born.
This is Microsoft's offering for an enterprise management and automation tool.
PowerShell's original code name was Monad.
In fact, for a while, the associated file extension was msh.
And what made PowerShell different was that it was based on the .NET Framework,
which at the time drove everything at Microsoft. Because of this,
PowerShell is an object‑oriented, or object‑centered language.
Instead of parsing text or manipulating output,
PowerShell commands work with objects in a pipeline.
And once you buy into this paradigm,
you'll realize how easy PowerShell is to learn and use.
PowerShell finally gave IT pros a standardized and easy‑to‑use
management tool that could be used interactively at a command prompt.
You type a command, and something happens.
But PowerShell is also an easy‑to‑learn scripting language.
Trust me.
As someone who once wrote a reference manual on Windows Script
Host and VBScript, PowerShell is super easy.
If you can run a command or two at a prompt, you can create a script.
Here's the timeline of how we got to PowerShell and
how PowerShell quickly matured.
PowerShell 1.0 is a far cry from where we are today,
but with each release Microsoft made it better.
And what you notice now is that PowerShell development is
accelerating. Even after all these years, Microsoft is making huge
investments into PowerShell, primarily because it plays a huge role
in their cloud‑focused business.
If you kept thinking Microsoft would drop
PowerShell and move onto something else, I think you'll be waiting a long time.