Comment by greener_grass
12 days ago
Bash is not a great cross-platform choice. Too many subtle differences.
The best way is a scripting language with locked-down dependency spec inside the script. Weirdly .NET is leading the way here.
12 days ago
Bash is not a great cross-platform choice. Too many subtle differences.
The best way is a scripting language with locked-down dependency spec inside the script. Weirdly .NET is leading the way here.
Stick to posix shell and it will run anywhere and on anything no matter how old.
Python with uv seems decent in here too.
python does EOL releases after 5 years. I guess versions are readily available for downloading and running with uv, but at that point you are on your own.
bash is glue and for me, glue code must survive the passage of time. The moment you use a high-level language for glue code it stops being glue code.
Hard disagree... I find that Deno shebangs and using fixed version dependencies to be REALLY reliable... I mean Deno 3 may come along and some internals may break, but that should have really limited side effects.
Aside: I am somewhat disappointed that the @std guys don't (re)implement some of the bits that are part of Deno or node compatibility in a consistent way, as it would/could/should be more stable over time.
I like Deno/TS slightly more because my package/library and version can be called directly in the script I'm executing, not a separate .csproj file.
>Too many subtle differences.
Such as?
This entire list: https://www.shellcheck.net/wiki/
How is any of that a subtle difference between platforms?
The tools you will call from your bash script differ in subtle ways between Linux, macOS, MinGW.
One good example is `uuidgen`
>uuidgen
That's neither a standard CLI utility nor a bash builtin.
1 reply →