@minego @jacobydave Er, #awk is often driven by #regex selection. I don’t know where you got the idea that was #sed’s exclusive domain.
@mjgardner @minego @jacobydave awk instills this incredible calmness over me, whereas what I try to solve with sed involved me spinning multiple plates in my head. Entirely subjective, but there you have it.
Incidentally, awk reminds me a little of Mark IV, a record processing and report writing lang I used in the 1980s on IBM mainframes.
@qmacro @mjgardner @minego I know that one works with columnar data, which is great for a lot of uses that could be useful for me, but rarely are in the 21st century. I know the other uses regexes. And I use neither enough to tell which is which.
@jacobydave @qmacro @minego Re: current 21st century data, I think #jq is the #JSON-driven spiritual successor to #awk’s streams of records and fields: https://jqlang.github.io/jq/
For early 21st century #XML, I remember #xmlstarlet, but it’s fallen into disrepair: https://xmlstar.sourceforge.net
@mjgardner @jacobydave @qmacro @minego I'm fond of shell scripting for my XML and JSON tasks, thought I'm particular about which shell.
@randomgeek @mjgardner @qmacro @minego I have nushell installed but I haven't really done anything with it yet.
@jacobydave @mjgardner @qmacro @minego I haven't needed to do anything interesting with Nu for a few months. Mostly just using it as a basic shell with tidy ls.
Maybe I'll putter at something this week.
@mjgardner #nushell on windows feels more unixy than much else on this platform for shure ;)