zsh because I've been using it since college and I don't like change
this post was submitted on 21 Jun 2024
131 points (97.1% liked)
Linux
48044 readers
770 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 5 years ago
MODERATORS
Fish for interactive shell. “It depends” for scripting, but usually ends up Bash since it is the NixOS default.
At the moment I'm using zsh with powerlevel10k. But powerlevel10k is not really supported anymore, and seems to be basically on life support. While it still works for now, I have been thinking of switching over to fish. But the lack of posix compatibility is holding me back a bit.
Bash, not because its my favourite but because it's nearly ubiquitous. I don't want to have to think about which shell I'm using.
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).
PowerShell, because of autocomplete and shift+arrows select.
I often end up in ps because I'm more familiar with it. But only if I have to do some scripting or so.
I use mainly fish and occasionally nushell.
Fellow Fish user here! 👋🏻
Powershell, but heavily customized.
Why the downvotes? Ps is pretty good and it works well on Linux too.
Swisher sweets but backwoods works too
oksh
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
POSIX on servers, thinking of switching to POSIX on desktop but that's a bit awkward
zsh
Nushell
Zsh with powerlevel10k + a few plugins
Fish for an interactive shell, and I'll often drop back to bash for writing a script. I can never remember how to do basic program flow in fish. Bash scripting is not great, but you can always find an example to remind you of how it goes.
Xonsh. For basic use (running CLI programs with arguments) it works like any other shell, and for other uses it has nice Python syntax (and libraries!). For example, I like not needing a separate calculator program, as I can do maths directly in the shell with an intuitive syntax.
I have customized ZSH to be very similar to Fish
While fish is easy to set up, I can't even be arsed to do that most times, so bash ends up being the one I use most.
PowerShell, with zsh being a close second
Feeling risky today, eh? Mind sharing the reasoning behind your extravagant choice?
Not sure what's extravagant about it... Fully object oriented pipeline in a scripting language built on and with access to the .NET type class system is insanely powerful. Having to manipulate and parse string output to extract data from command results in other shells just feels very cumbersome and antiquated, and relies on the text output to remain consistent to not break
PowerShell, it doesn't matter if more or less data is returned, as long as the properties you're using stay the same your script will not break
Filtering is super easy
The Verb-Noun cmdlet naming convention gets a lot of (undeserved) hate, but it makes command discovery way easier. Especially when you learn that there's a list of approved verbs with defined meanings, and cmdlets with matching nouns tend to work together.
It actually follows the Unix philosophy of each cmdlet doing one thing (though sometimes a cmdlet winds up getting overloaded, but more often than not that's a community or privately written cmdlet)
It's easily powerful enough to write programs with (and I have)
And it works well with C#, and if you know some C#, PowerShell's eccentricities start to make way more sense
Also, I mainly manage Windows servers for work running in an AD domain, so it's absolutely the language of choice for that, but I've been using it for probably close to 14 years now and I can basically write it as easily as English at this point
Zsh on workstations. Bash on servers.
xterm+zsh
zsh, because of highly customizable.
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.
Soft shell tacos are my favorite. Hard shell is ok but there's nothing like a double wrapped soft taco.
Oh and I just use bash.
Pff, newbie. I bash my tacos!
/s
Fish & dash.
Microsoft copilot
Favorite would be a highly customized zsh.
fizsh (not fish) is what I actually end up using, as I can't be bothered to copy that config around and retune it for each machine. Gives me the syntactic sugar of zsh with common default options on by default, an OK default prompt, and doesn't break POSIX assumptions like fish. Also Installs quickly from the package manager without needing to run through the zsh setup each time - unlike oh-my-zsh. And if I still need customization, all the zsh options are still there.
bash is so ubiquitous that I never considered anything else.
Don't try zsh, because you won't be able to go back to bash after that 😉
view more: next ›