News for hackers. Stuff that matters.
Re:Jq – A Command-line JSON processor by kbenson on Monday April 27, 2015 @02:15PM (#9448139)
I understand this, I myself often trade off between bash and Perl. Sometimes I'm using a for loop on a shell expansion to tar directories, sometimes I'm piping an ls to xargs to parellelize a workload, but often I'm piping SQL output to Perl, selecting the records I care about and storing (and/or altering) the relevant fields in a data structure, and outputting the data in a formatted way (such as SQL update/insert statements) or reporting some aggregate information.

What I see in PowerShell, which to be truthful I never use (it's not in my common environment), is a less powerful/extensible version of Perl, but optimized for a specific workload, as there's less parsing and manipulation of data required if it's easily available in the formats you need already. Honestly, I still wouldn't use much it if it was installed by default on all UNIX boxes, because Perl fills that need for me, but I recognize what it's trying to do on a conceptual level, and it's similar to what I end up doing every day, so I support that.

Re:Jq – A Command-line JSON processor by alttab on Monday April 27, 2015 @09:02PM (#9450048)
You have it backwards. Even though they are similar on a conceptual level to what you do everyday, doing it in Powershell requires buying development tools. And there hasn't been a need to support that monetarily for a while.
Re:Jq – A Command-line JSON processor by lmz on Monday April 27, 2015 @09:24PM (#9450115)
What development tools do you need to buy for Powershell? (unless you mean Windows itself).
Re:Jq – A Command-line JSON processor by zobzu on Tuesday April 28, 2015 @09:06PM (#9456004)
hmm i do powershell stuff with "just" windows amd gvim.exe
Re:Jq – A Command-line JSON processor by alttab on Sunday May 03, 2015 @09:00PM (#9483778)
just windows