zlacker

[parent] [thread] 2 comments
1. mmh000+(OP)[view] [source] 2026-01-07 18:54:47
I really would like a new shell that wasn't based on a poorly designed programming language from the 1960s[1][2]

However, I need to know sh/bash well because they're the tools installed by default; in any "well-established" organization, getting approval to install a new shell will range from "12 to 24 months" to "impossible". And without that, I'm not going to put in the effort to learn a new tool that is only useful some of the time and requires massive context switching.

[1] https://en.wikipedia.org/wiki/ALGOL_68 [2] https://en.wikipedia.org/wiki/Bourne_shell#:~:text=Stephen%2...

replies(1): >>BadBad+a7
2. BadBad+a7[view] [source] 2026-01-07 19:26:57
>>mmh000+(OP)
That's what I mean. A new shell would need to blow me away with some amazing must have interactive feature. The scripting part is, at least for me, not really relevant. If I can install software on the target I will install a proper language and if not then it will be bash or sh anyways, even though they properly suck.
replies(1): >>ZenoAr+0s
◧◩
3. ZenoAr+0s[view] [source] [discussion] 2026-01-07 20:53:47
>>BadBad+a7
The "killer app" is that it's easy to string together multiple commands and have them work more reliably than shells that rely on plaintext. In other words, it's something in-between running individual commands and writing full scripts. I've not used Nushell before, but I'm very familiar with PowerShell which is similar, and it's ridiculously easy to manipulate and explore your file system with confidence that you don't have to rely on hacky and hard to read regex and similar suboptimal solutions.
[go to top]