If your script starts with , 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.
Like, why is bash ancient? (3.2 vs 5)
To avoid GPLv3, zsh is the new default.
Why is there no package manager
Mac App store is the official one, can also install brew, macports, pkgsrc, or nix. Or use language/runtime specific ones like npm, pip, cargo, go.
Why are the utils like ls and friends flag-order-sensitive
They avoid GNU versions of utilities, for similar licencing fears as avoiding modern bash. That said ls . -lah is unhinged, I don’t know any other unix derived ls that supports that.
Why do I have 40 network devices with cryptic names?
Yeah they got some weirdo Apple stuff
I remember when I was a kid messing with Windows 95/98, I had this intuitive feeling of what was happening under the hood. Just like how you describe your theory. Honestly you’re probably on the right track. In theory on linux you can actually dive into the source code and try to figure out what’s actually happening, but that’s intimidating AF. Hard to say if the problem is between wine and the Direct Rendering Manager (DRM), X11, Wayland, KDE, or the GPU driver…
I had a kind of similar problem with my display not outputting when it was connected. I had to use a DRM file in /sys and udev script to fix it, wrote a blog about it. If your monitors are still messed up after a reboot, it sounds like this won’t help you though.
Also you made me lol to “wine strikes me more as an emulator”. It totes is. The “Wine Is Not an Emulator” name is a joke, the original name was “WINdows Emulator”, which they changed to avoid Microsoft’s lawyers.
That is simultaneously ridiculous and amazing. Blindly clicking the buttons to enable the screen definitely proves you’re getting familiar with the OS.
Why do you think wine/Bricklink messed it up in the first place?
This from the company that started the netbook trend with the $400 eeePC in 2007…
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.