4 ms·
From 2014 [1]. This seems to be posted once per year (at least); however, hardly a complaint as the discussion tends to be high quality. My personal mantra is
by heybrendan 1y ago
From 2014 [1].
This seems to be posted once per year (at least); however, hardly a complaint as the discussion tends to be high quality.
My personal mantra is if it's over 10~20 lines, I should arguably be using another language, like Python (and perhaps correspondingly, subprocess [2], if I'm in a hurry).
[1] https://web.archive.org/web/20140523002853/http://redsymbol.net/articles/unofficial-bash-strict-mode/ https://web.archive.org/web/20140523002853/http://redsymbol....
[2] https://docs.python.org/3/library/subprocess.html https://docs.python.org/3/library/subprocess.html
- esafak 1y agoIt's time to stop using these archaic shells, and make sure the newer ones are packaged for and included with popular operating systems. Better scripting languages have been offered in shells for a long time: https://en.wikipedia.org/wiki/Scsh https://en.wikipedia.org/wiki/Scsh These days I've settled on https://www.nushell.sh/ https://www.nushell.sh/
- tux1968 1y agoI think https://oils.pub/ https://oils.pub/ has a good shot at being the eventual replacement because it has a very strong transition story. Being backward compatible, while allowing you to progressively embrace a modern replacement, is pretty powerful.
- ZYbCRq22HbJ2y7 1y agoi don't think nushell is better than bash for day to day things. it is nice when you need it though, and then you can just run it, like with any shell.
- esafak 1y agoWhy would you do that when nushell is strictly better? It's bash that I drop into when I rarely need to, which is when someone gives a bash recipe, not nushell.