News for hackers. Stuff that matters.
Re:Filenames and Pathnames in Shell: How to Do It Correctly by IshKebab on Tuesday June 20, 2023 @04:57AM (#36401394)
The only real reason to use Bash in the first place is that people will probably have it installed already (assuming you don't care about the most popular desktop OS in the world).

If you're going to add a dependency you may as well just use a "real" language at that point.

I've been using Deno for "shell scripts" for a while and it's great. My only complaint is that `deno run` prints annoying "a new version of Demo is available" messages which it very clearly shouldn't. Hopefully they'll fix that.

Re:Filenames and Pathnames in Shell: How to Do It Correctly by maleldil on Tuesday June 20, 2023 @07:49AM (#36402701)
> If you're going to add a dependency you may as well just use a "real" language at that point.

Not necessarily. It's still easier to manipulate shell programs in fish[0] than it is in Python since fish was made explicitly for that. Calling external programs, using pipes, process substitution, etc. are easier in a "proper" shell language.

[0] Or any bash alternative of your choice: nushell, oils, xonsh, elvish, etc.

Re:Filenames and Pathnames in Shell: How to Do It Correctly by harrisi on Tuesday June 20, 2023 @11:17AM (#36405223)
I don't know if they're planning on changing that, but `-q|--quiet` will suppress this. It just sets the log level to error, and the new version message is info level.