Linux

48082 readers

1159 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

[email protected]

zsh or fish for an intermediate Linux user? (sh.itjust.works)

submitted 1 year ago by [email protected] to c/[email protected]

63 comments fedilink hide all child comments

So I've been using Linux now for a while, and am looking to migrate my dev environment to vim and spend more time in the command line. I'm fairly comfortable with bash but by no means an expert. I've used zsh with some minor customization but just recently learned about fish. I'd love to hear people's opinions.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 1 year ago (1 children)

That's why I included Perl, it is always there. Just don't code as if you were in the nineties and Perl is a perfectly legitimate language, even more so for shell tasks. Bad and good doesn't depend so much on the language but the coder.

[–] [email protected] 1 points 1 year ago

Bad and good doesn't depend so much on the language but the coder.

IMO there's also a component where a good coder will pick the best suited language for the task, but will also pick something that the rest of their (potentially less skilled, junior or even intern) team won't be scared away by.

If you're mostly just running a few commands and writing to a bunch of files, bash is great and does that in almost no code and remains quite readable. Like, a backup script for a database is essentially a bash one-liner. I'm sure it's also easy in a Perl script, but just seeing a .pl file can scare some admins whereas they know what to expect if they see a .sh.

Then there's also a component of, what does the company uses. If the company runs Ruby apps, then I'd write tooling in Ruby. If the company runs PHP apps, some of the tooling will be written in PHP.

It's very circumstantial in the end. I'll definitely whip up some Perl if it's advantageous, but really most of the time it's just wrapping an rsync or whatever, and at work it's usually just some glue or bootstrapping something like Puppet or Ansible. Not a fan of those personally but it's a safe bet for my role and industry.

On the personal side, I tend to turn to what's my favorite language at the moment, so lately I've been practicing my Rust.