Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
If you ever copy paste commands you don't understand (and aren't prepared to take a detour down a rabbit hole to figure out why they didn't work), stick with bash (or zsh).
Fish isn't "posix compliant" which can make some things work (or not) unexpectedly.
Don't get me wrong, it's a great shell and there are many reasons people emulate its behaviors in other shells, but I can't recommend it as a "newbie" or "casual user" choice.
I most definitely copy and paste commands that I don't understand. I even use LLMs to help write simple Bash scripts. :)
I was just curious what the use cases are for this shell as I've only ever used Bash.
It's a very user-friendly shell... except for the posix compliance.
Everyone I know who (still) uses it daily accepts that they have to translate back and forth and still write scripts in bash (or sh).
If you wanna give it a go, by all means. It's just as easy to switch as to switch back. You can always drop into bash and try a command again too.
I never have to write scripts in bash after having switched to fish. I just write all my scripts in fish. 🤷♂️
It's unfortunately not that easy when you're using Linux at your job or want to be able to share your scripts with others...
Like, Bash for scripting is quite cursed, but people will typically still prefer using it over learning a new language.
I use Linux for my job but luckily I don't have to share scripts with anyone. 😌
Not to mention some environments don't let you install anything other than what's already on the box. Both sh and bash generally are available.
Ah, good point. In many cases, you also don't want to install an alternative shell, like if you're dealing with lots of containers and would need to make Fish available in each one.
Although, I will say that more recent versions of Fish are available as a standalone executable, so you don't have to install it in the traditional sense. You can probably transfer it together with your script file in most cases. That's a relatively new/experimental feature of Fish, though, so no idea how well such a workflow goes in practice.