this post was submitted on 03 May 2026
173 points (86.2% liked)
Technology
84377 readers
3485 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
None of these are good reasons for it to be like this.
zsh is much better than bash tho
but it isn't available anywhere else so I can't use it for scripts that get distributed.
If your script starts with
#!/bin/bash, both bash and zsh will run it fine. The bigger problem is the programs, filesystem and libraries being different. Which is why POSIX exists, if you're looking to write stuff that works across systems.I couldn't tell if you were honestly asking for explanations or if all of your complaints sum up to "it's different and I don't like that". Which honestly, fair.
not exactly. if you're worried about the differences between bash 3 and 5, you're probably using some intermediate bash-exclusive features because that's the headlining changes between these versions (google says associative arrays and new shellvars. even if zsh has equivalent features, the syntax would be different.) it's only "guaranteed" to run fine in both shells if the shebang ends in
/shto call the POSIX shell without any bash- or zsh- specific features.i don't get what @greyscale@lemmy.grey.ooo means by this though
Production server does not have zsh. Other developers aren't on macbooks. Ergo, I cannot use zsh (it sucks anyway)
bash 3.2 means that no, it wont run.
What bash scripts are you writing that you expect to run on both a Mac laptop and a production linux server? You can install the newer bash if that's what you're used to, but you're surely going to run into issues like
ls . -lahfar quicker than differences in bash since 3.2Even on a linux desktop you're going to have differences from a production server, you'd want to be using something like ansible, or replicating production in a local test environment in a container or VM. Exactly like you have done.
How'd you end up being the only one at your workplace to be given a Mac? Even with a linux VM, being on ARM can cause issues with compatibility.
Yes, the flag ordering is infuriating.
Everything is in docker containers because macos is contaminated.
And I'm not, its just the crayon-users like macos so I'm stuck with it. Its a tonka-toy OS I'm being subjected to and its infuriating. I don't know why these things are popular, the keyboards are heinous and the screens are smeary blurry over-driven messes.
And the OS stinks.