I've always struggled with actually retaining knowledge on how to use the myriad tools you'd usually need to extract/parse data (awk, sed and friends) and this was a game changer. I don't quite daily drive it just yet but when I do need it, it's vastly more ergonomic.
love to read fellow* people in the unix world discovering what made powershell great 10+ years ago as though it's a paradigm shift. and the top comment of the thread is still nitpicking the points in the post while missing the forest for the trees. I mean ifconfig as an example is lol but still.
like powershell's got such bizarre warts and design choices and it's more ergonomic than unstructured text pipelines despite that
i know it's not that simple but still, lol
*linux has been my primary os for 9+ years, not throwing stones here
While jc is a great tool, and I'm definitely a fan, I believe the real solution to the overarching problem lies in a paradigm shift: see nushell
I actually use both! It's so nice to just
jc git logand then work with the data using nushell :)Oh that’s smart! And then nushell just handles the data for you…I might try that!
I've always struggled with actually retaining knowledge on how to use the myriad tools you'd usually need to extract/parse data (awk, sed and friends) and this was a game changer. I don't quite daily drive it just yet but when I do need it, it's vastly more ergonomic.
love to read fellow* people in the unix world discovering what made powershell great 10+ years ago as though it's a paradigm shift. and the top comment of the thread is still nitpicking the points in the post while missing the forest for the trees. I mean
ifconfigas an example is lol but still.like powershell's got such bizarre warts and design choices and it's more ergonomic than unstructured text pipelines despite that
i know it's not that simple but still, lol
*linux has been my primary os for 9+ years, not throwing stones here