#Bash scripting is straightforward enough that I can edit existing scripts without actually knowing how to write the scripts myself. If I'm proficient in #python is there any point in learning bash scripting. Is there something that I can do in bash or that bash makes easier that makes it worth learning.
I want bash scripts, but with conveniences and lightweight dependencies that can be inlined.
Imagine a "direnv-like" standard library of functions, alongside the ability to fetch-if-not-installed certain binaries, and maybe even a super simple module system.
Then, you bake the script, and it becomes a single file bash script.
To be clear, I want to write it in bash, and have it turn into "bash that I can curl".
Pretty shure this would require either a derivative language [i.e. "enhanced bash" / "ebash"] or require some preprocessor approach like #Blitz [#BASIC] and #Sass [#TypeScript]...
@hazelweakly@jbminn how about #zsh? I dunno if you have something that youd describe, but getting there should be easier woth zsh than with #bash
basically because path resolution in the earlier makes sense. I remember several "pls source .direnv-or-somehting if it exists" plugins exist, but for use in interactive shell and they don't evaluate super directories (again, should be easier to implement in zsh)
I also do electronic #musicproduction in #Reaper. I intend to finish my first album sometime this year. We'll see if I can throw some music up on the internet anytime soon.
Due to various gaps in APIs, SDKs, CLIs, etc., I still have some significant cloud service lifecycle management that happens through #bash or #python scripts that run on a cron (or whenever someone remembers to run them). Like 99% of stuff is automated via Terraform, Ansible, Jenkins, etc., but there is some severe jank around the edges of absolutely everything on the internet. #devops
New post: Improving my interactive #jq workflow with ijq, #bash and #tmux.
I'm a big fan of ijq and how it allows me to explore #JSON data interactively with jq expressions. With a small script I have improved my workflow by being able to capture the jq expression from ijq and use it easily on the command line.
Rather than deciding on a scripting language that only some in the organization understands and enjoys — like #Python — consider a more inclusive option, like #Bash, which no one understands or enjoys.
#MastodonHelp
Is there any tool to download public posts and retoots and reply toots of an inactive Mastodon account? I forgot to backup my posts before migrating, and I don't know a method that doesn't involve disabling inactivity on the account (and not sure what that will do).
This is hilarious. A #Google engineer invented #zx to make command line scripting easier with #NodeJS, because at a certain point #shell scripts get too complicated and you need a Real #Programming Language.
This is exactly #Perl’s use case from thirty-six years ago. But the kids want #JavaScript everywhere and would rather it take more work to convert their ascended #Bash scripts to a vastly different syntax.
https://fuckgov.org/@h Oh, I don’t deny it’s useful. And you’ll never catch me saying it’s bad to stick with what you know if it gets the job done—that’s one reason I continue to use #Perl.
My main point was that it’s less work converting #Bash to Perl than to #JavaScript.
The “kids want JavaScript everywhere” was admittedly a little snark directed at the “continuous amnesia” of prior art (not unique to #JS developers but their sheer number means it’s really prevalent) as described here: https://www.ufried.com/blog/continuous_amnesia_issue/
Your reply is to a post where I specifically said the point was about converting from #Bash.
If you don’t know how to read a #shell script you definitely don’t know how to convert it to another #programming language. You’ll be doubly handicapped if the new language is nothing like the old.