true. Increasingly commands can output their return as json, but then jq is also not as easy to handle as I sometimes wish. Maybe oils "quoted string notation"

true. Increasingly commands can output their return as json, but then jq is also not as easy to handle as I sometimes wish. Maybe oils "quoted string notation" (QSN) for safer passing of strings can be of interest to you: http://www.oilshell.org/blog/2020/10/osh-features.html#safe-processing-of-user-supplied-data-like-filenames http://www.oilshell.org/blog/2020/10/osh-features.html#safe-... Concerning Powershell the author of oilshell addresses how shells are native to their surroundings in http://www.oilshell.org/blog/2021/01/philosophy-design.html#situated-languages-powershell-vs-oil http://www.oilshell.org/blog/2021/01/philosophy-design.html#... - he'll be attending the HotOS panel too. Implementing WSL2, native openssh in Windows, the use of bash, it must be to stay relevant. Edit: and I think this thread will interest you too - https://lobste.rs/s/k10sfa/why_did_i_write_my_programming_projects#c_mnauw8 https://lobste.rs/s/k10sfa/why_did_i_write_my_programming_pr... and the sustrik/uxy reference within