Rust

7950 readers

11 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

EdTheLegendary@programming.dev

torcherist@programming.dev

Release fish 4.2.0 (github.com)

submitted 5 months ago by lens0021@programming.dev to c/rust@programming.dev

5 comments fedilink hide all child comments

cross-posted from: https://programming.dev/post/40520896

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

[–] flying_sheep@lemmy.ml 1 points 5 months ago* (last edited 5 months ago) (1 children)

Idk if that'll make you happy. The different POSIXy shells have so many subtle differences and footguns that I personally feel best

using nushell as a daily driver, as it's sane and makes sense and errors out when it should
using bash when forced to interact with things that are written in bash (I don't know anything written in fish or ZSH)
using Python or Rust or so for scripts living in projects that are written in that language

I can't be bothered to look up the weird arcane sigils that make bash not shit itself when e.g. using arrays as command args or so, so I will author only the most pedestrian bash scripts where pipes are already a bit much.

[–] TehPers@beehaw.org 2 points 5 months ago

I already do #1, and I push for #3 (specifically Python or TS) where I can at work, but there's this weird obsession with bash that people have at work despite all these scripts not running on Windows natively (outside WSL). Currently I do #2, but I often end up just stuck in bash the whole time because it's needed for things as simple as building our code. I want to try out Fish as an alternative for those situations.