3 ms·
We might have very different use cases I guess. I script a lot to work with data, not to automate things. I feel very comfortable getting a stream of data and
by NetStrikeForce 11y ago
We might have very different use cases I guess. I script a lot to work with data, not to automate things.
I feel very comfortable getting a stream of data and treating it with sed, awk, grep and whatever; but once I worked with objects it feels much more data-oriented.
And please don't get me wrong, I've been in love with Bash since a Slackware CD fell on my hands in the 90s. I just was mind-blown by PS after making fun of it for years - just because the default terminal where it runs is less than great.
I guess this thread proves the point of bringing Bash to Windows: Different people, different uses, different needs and solution. And that makes me happy :)
- tripzilch 11y agoso is there a better terminal available for PowerShell? (preferably for win7, because I run Linux at home and win7 is the most likely platform I may spend some time elsewhere) I do appreciate, from all I've heard about PowerShell, it might be an interesting environment to try some scripting in. The actual shell/programming language can't be (much) worse than bash--I mean let's admit, bash is pretty ancient and therefore didn't have the advantages of progress in designing programming languages we have made in the past decade(s).
- NetStrikeForce 11y agoThe terminal is inferior IMHO, but the language is far superior. Of course, if you're too used to Bash and its paradigm there's a learning curve in PowerShell. Not steep, though :-) The killer features for me are the objects and being able to seamlessly use C# libraries in my scripts.