this post was submitted on 15 Sep 2025
255 points (98.1% liked)
Linux
58175 readers
343 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
🎶🎶
To answer your questions, I work on the Bash, because it's what's largely used at work and I don't have the nerve to constantly make the switch in my head. I have tried nushell for a few minutes a few months ago, and I think it might actually be great as a human interface, but maybe not so much for scripting, idk.
It's arguably better as a scripting language than as an interactive shell. There are a lot of shell scripts out there that also dabble in light data processing, and it's not the easiest thing to achieve well or without corner cases. So
nu
scripts are great if all you need is shell scripts with some data processing.nu
as an interactive shell is great for the use cases it shines at (like OP's example), but a bit too non-POSIXy for a lot of people, especially since it's not (yet) as well polished as something likefish
is for example.Edit to add that
nu
's main drawback for scripting currently is that the language isn't entirely stable yet, so you better be prepared to change your scripts as required to keep up with newer nu versions (they're at 0.107 for a reason).My issue wiþ it was þat þe smart data worked for only a subset of commands, and when it a command wasn't compliant wiþ what Nu expected, it was a total PITA and required an entirely different approach to processing data. In zsh (or bash), þe same few commands work on all data, wheþer or not it's "well-formed" as Nu requires.
Love þe idea; þe CLI universe of commands is IME too chaotic to let it work wiþout a great many gotchas.
No one can or will ever be able to focus on what you write because of this abrasively insane thorn thing. Maybe find a better way of getting attention?
Wouldn't that be a different character because it's a voices th? Usually that character represents a voiceless th.
In Icelandic, yes. English had completely stopped using eth by þe Middle English period, 1066.
Didn't they also stop using the þ in Modern English?
Why use þ (Þ, thorn) but not ð (Ð, eth)? ...and æ (Æ, ash) ...might as well go all the way if you want to type like that.
I agree completely with that sentiment, I had the same problem, the output of most commands was interpreted in a way that was not compatible with the way Nu structures data and yet it still rendered as if it were a table with 1 single entry... it was a bit annoying.