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.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I've recently migrated to nushell, I don't straight up recommend it because it's not POSIX compliant, so unless you're already familiar with some other she'll I would not use it.
That being said, it's an awesome shell if you deal with structured data constantly, and that's something I do quite often so for me it's a great tool.
Just looking at it briefly it looks a lot like PowerShell, any reason to use it over PowerShell?
Never used PowerShell, so I didn't know that it was available for Linux nor open source, since from a quick search both of them seem to be true I guess there's no real reason since both are described very similarly.
It's indeed a lot like powershell, but I found it to be much less painful to use for everyday tasks. I can't really put my finger on it, but powershell always felt very clunky and unpredictable to use. With Nushell, I can write pipelines that usually have the desired behavior on the first try. Also, its more convenient in so many different aspects that I can't go back anymore.
The biggest downside is, that it hasn't had a stable release yet. While I haven't encountered any bugs yet, there are often breaking changes with new releases that may break your scripts.
Yeah, PowerShell does do things that don't exactly make sense without having some understanding of the underlying dotnet and what the components actually do
Like I said, never used PowerShell, but yeah, nushell pipes are very intuitive, I've been only using it for a short time but was already able to do very interesting pipes with minor effort
Fish for interactive shell. “It depends” for scripting, but usually ends up Bash since it is the NixOS default.
Bash is my favourite one, second to it being Fish
oksh
Bash. By default it might seem less featureful than zsh.. but bash is a lot more powerful and extensible than some give it credit for. It might be more complex to set it up the way you like it, but once you do it, that configuration can be ported over wherever bash exists (ie. almost everywhere).
Nushell
Bash, zshell, BusyBox....you don't really need anything else
I use mainly fish and occasionally nushell.
Zsh with powerlevel10k + a few plugins
Bash as it is what I'm most familiar with. Having an eye out on the https://amber-lang.com/ that compiles to bash for future scripting purposes.
Bash, just because everything else already uses it. That and bashisms have infected nearly all of my scripts as I clumsily bump into the limitations of POSIX string manipulation.
I have found some very fun things with sed branching patterns as a result of these limitations though...
https://www.gnu.org/software/sed/manual/html_node/Branching-and-flow-control.html
zsh because I've been using it since college and I don't like change
I have been enjoying fish a lot over the last few months, but I generally try to use Bash, it makes cross-*NIX administration that much easier.
xterm+zsh
PowerShell, with zsh being a close second
Feeling risky today, eh? Mind sharing the reasoning behind your extravagant choice?
Bash is my login shell, but I have fish set as the default shell for alacritty
POSIX on servers, thinking of switching to POSIX on desktop but that's a bit awkward
zsh with grml config because I'm too lazy to make my own config.
Zsh on workstations. Bash on servers.
Microsoft copilot