PowerShell is open sourced and is available on Linux

Post by haberman » Sun, Aug 21, 2016, 8:32 PM UTC

inimino wrote: post #773

haberman wrote: post #453

Earlier quoted context omitted.

> You are considering it just RAW text when it is actually formatted text that has been parsable for years with common unix command line tools. Parsing command output with sed/awk/etc (ie. "common unix command line tools") is absolutely an ad hoc parser. Let me give you an example that I recently ran into. I have a tool that parses the output of "readelf -sW", which dumps symbols and their sizes. The output normally…

The Unix answer is why are you using a regex on tab-separated values? Wrong tool for the job. Of course the problem with Unix is that there are a thousand different semi-structured text formats, edge cases, and tools that must be mastered before you can make any sense of it all. Any time you point out the pain a Unix fan can just respond by pointing out your ignorance.

    Symbol table '.dynsym' contains 164 entries:
       Num:    Value          Size Type    Bind   Vis      Ndx Name
         0: 0000000000000000     0 NOTYPE  LOCAL  DEFAULT  UND

Post by emodendroket » Mon, Aug 22, 2016, 1:45 PM UTC

qwertyuiop924 wrote: post #457

emodendroket wrote: post #162

Earlier quoted context omitted.

OK, but now imagine it's not a database, because there are programs that do act this way.

And those programs usually emit proper CSV. You could use regex to match on what you want, but AWK was literally built for this. It's fantastic, it works great, and if you don't use that tool that was built to solve your problem, that's your own lookout.

Post by uep » Mon, Aug 22, 2016, 3:18 PM UTC

jupiter90000 wrote: post #443

uep wrote: post #110

Earlier quoted context omitted.

Powershell isn't competing with bash, it's competing with Python. So then, how does it compare against Python? While plenty of small scripts are still done with bash, I think Python is pretty common for serious production needs. I use it for virtually all scripting these days. I had a recent experience where a developer spent a day and couldn't get Powershell's webrequest library to do what he wanted. I was able to a…

Sure, there are different ways to do various things, especially depending on what one is familiar with and what the task at hand is. It sounds more like you knew how to get something done with your tools faster than the other guy/gal in this case. :)

Post by qwertyuiop924 » Mon, Aug 22, 2016, 5:07 PM UTC

emodendroket wrote: post #783

qwertyuiop924 wrote: post #457

Earlier quoted context omitted.

And those programs usually emit proper CSV. You could use regex to match on what you want, but AWK was literally built for this. It's fantastic, it works great, and if you don't use that tool that was built to solve your problem, that's your own lookout.

I don't think awk is actually capable of parsing CSVs in all cases.

Post by greyfade » Thu, Aug 25, 2016, 9:12 PM UTC

progman wrote: post #706

CrLf wrote: post #506

Earlier quoted context omitted.

After a number of years using PowerShell, my conclusion is the opposite: text "scraping" is just better for most cases. Normal shell usage means doing a lot of one-shot pipelines incrementally. This is just easier and faster to do when passing text around because you can look at it and not have to inspect some object for it's type and what attributes/methods it provides. Parsing the text is not the problem here (alth…

> text "scraping" is just better for most cases. Unix pipes handle bytes, not just text. For instance, copy a hard disk partition to a remote hard disk via ssh: (dd if=/dev/hda1) | (ssh root@host dd of=/dev/sda1) The KISS principle ("Keep it simple, Stupid") is the best way in many cases. In Unix you can quickly enter a pipe without special coding which does also non-trivial stuff. For instance, find -name "*.xls" -e…

    find -name '*.xls' -print0 | xargs -0 xls2csv