The complaint really is that if everything is sequential it is a fault in the language to make you explicitly say it every time, not that await is somehow worse than promises.
When I need to run something async in Bash I can just add a `&`. Done. The majority of my scripts are purely sequential, though, as the language lends itself well to sequential data processing/piping.
I'm not seeing a benefit by wrapping almost every single command in 'await $`...`'. I get why you'd want to wrap Bash in a different language, especially when handling numbers. But I'd rather use something like Python than this verbose trickery.
I agree. My scripts are also rigidly sequential and verbose which is easier for me and other devs after me to have a simple mental model of what is going on at a glance. Which I think saves time in the long run because any dev can easily understand and make intelligent additions to make it better. For complex scripts, Python is the goto and isn't terribly difficult to grasp either.
I didn't say it was, but in the example given basically everything was, hence the complaint the parent made was that in JS we are often writing a lot of await, or promises or what have you because we have a lot of things that need to be done sequentially in a particular part of the program, or, in a small script, where everything needs to be sequential.
It's not really a JS issue here, just the ZS project decided to make `$` function async (for some good reason I'd think) but they could have gone the other way and make it synchronous by default.
I don't believe this is a language specific choice, they could have done the same with C#
