4 ms·
How did you finally get into it? I was stoked about it 15 years ago when I first read about it, but using it never clicked with me. Every now and then I enthusi
by AnonymousPlanet 6y ago
How did you finally get into it? I was stoked about it 15 years ago when I first read about it, but using it never clicked with me. Every now and then I enthusiastically try to embrace it, just to eventually be annoyed by all the clumsiness, lack of speed, or about having to wade through layers of objects just to get to the information I need. It just does not have the feeling of a tool for shell users honed by shell users, but a soulless navigation tool for a Byzantine object structure.
I finally decided Powershell is not so much a shell but rather an environment good for scripting.
What direction did you come from when embracing it? Did you have a strong background of Unix admin / developer use of shells?
- CraigJPerry 6y agoIt’s early days on my test drive. I don’t know how well it’ll fare for fairly common actions in bash like “here documents” or what the equiv of shopt extglob is in pwsh. My usual cli usage is what i’d call “text manipulation” - slicing and dicing command output or converting csv-like data in some way or another. My toolset is the usual suspects - bash, sed & awk but beyond a certain complexity i’ll switch to python. The key thing for me is i can still use grep, sed, awk and python in pipelines as before but i’m attracted by the easy data access in pwsh. The idea that Get-Process returns an object and i can just query each process’s WSS attribute for example is appealing right now (as opposed to explicitly manipulating text to suit, e.g. grep resident /proc/*/statm or ps -o rss or whatever approach)