Familiarity (does it breed contempt)
Many years ago, a college professor told us a story related to Unix - when Dennis Ritchie was asked a question as to what he regrets in C, Dennis Ritchie replied that he would add an 'e' to the 'creat' function. I do not know the truth of this story though Google may provide an answer.
The reason I remembered this story is simple. I wanted to post an article. Though I have a few in my kitty, most of them are not fleshed out. I wanted something smallish. So I searched my scratch pad. There I found a few PowerShell commands.
Many of us who do not have an aversion to the command prompt, particularly on Unix/Linux systems, will remember a vital debugging aide. Not the 'print' statement, but 'tail'. When executing a large application with many print / log statements, using 'vi' or 'more' or 'less' is not helpful. This is because new data is being appended to the file and none of these tools keep refreshing the data. So the invaluable command was 'tail -f app.log'. This command keeps reading data from the file as it is updated and keeps adding that text to the console, causing the text to scroll, effectively allowing us to look at the log as it is generated and also scroll up to view previous messages.
For many years, this command has been sorely missing on Windows. Windows introduced PowerShell for a more rich command line scripting experience but uses a verbose syntax. Thus
tail -f [file-name]
becomes
Get-Content -Wait -Tail 30 [file-name]
Similarly,
wc -l
becomes
Get-Content [file-name] | Measure-Object -Character
Get-Content [file-name] | Measure-Object -Word
Get-Content [file-name] | Measure-Object -Line
Get-Content [file-name] | Measure-Object -Character -Line -Word
In summary, having become familiar - over the years to the Unix/Linux syntax - this syntax feels too verbose. Initially, such a verbose syntax can give you the creeps. But the syntax will grow on you with familiarity. The good thing is that we now have feature rich scripting support even on Windows.