After some break I had to use Microsoft's PowerShell. Terrible experience.
What is this weirdo called PowerShell some would ask.
In the world of windows you must use a mouse to do what you are allowed to do.
But some tasks are often repeated for same objects (ex. files). In such a case you would use a shell script... but M$Windows has no such. So Microsoft created their own shell. They wanted to be better and mixed unix shell capabilities with .NET interface. They added their own implementation of pipe (process inter-communication). And the result is... tragic :(
I'm used to bash and ksh. I know them quite well. Both have their own limitations but are extremely powerful.
PowerShell has better potential... yet interface sux, syntax is very unpredictible and it is overall ver user unfriendly.
With bash and ksh I know some basics and it is wnough to create usable power scripts.
With PowerShell I need to learn it every time I get back to it, then I need to use google plenty of times and the result is miserable (I'm usually able to get my functionality but it takes a lot of time). And after a while I'm done and fed up so I leave powershell for some time and at some point I need to get back to it.
An alternative? cygwin, perl-for-windows, python-for-windows... many alternatives.
Summary:
Microsoft's PowerShell sux - they wanted to make it better but they did it as usually.
No comments:
Post a Comment