Google ZX – A tool for writing better scripts
https://news.ycombinator.com/item?id=39323986 (8 comments)
I've been using zx for a couple years now, it's a handy all-in-one library. It's gradually replacing my Bash scripts, and I tend to reach for it for any new shell scripting needs. With Bun's fast startup time, it's also gradually replacing Node.js and zx.
Now we have more choices and more innovation? Really exciting.
This suite of tools feels indispensable. Anything to keep me from having to write/maintain bash scripts that are more than a series of commands.
I get that there are contexts where portability etc are important, but my work is very far from such places.
I truly despise Bash and its brethren.
Haven't had this need in at least a year though. From looking on npmtrends[0], ShellJS still seems the incumbent and quite alive.
Are these new zx/dax/bun-shell tools, each inspired in the previous one, way better?
I haven't used bun shell at all.
Would this be possible license-wise? Also do you have any focus on cross-platform install commands (like apt/dnf/brew/winget ~~ complex and most likely out of scope I know!)
So it would result in magnitudes of more usage if it was integrated, which seems to be the path Bun is taking.
I still use `writeFileSync` and such out of habit, but I don't think I really need them since we got first-level await (out of async functions).
If you stick to Python until a winner emerges, how does that help you? You'd have some old scripts in python, and some new ones in WinnerJS, which I think it's worse than having some in WinnerJS and some in LoserJS.
Your LoserJS scripts won't stop working. At least Bun-shell and Dax scripts in the same language. Since Bun's got some inspiration from Dax, I'm sure the API won't be that different.
I'm usually not one to jump on new JS stuff, but writing scripts on any of these feels relatively low risk.
Also, I'm still maintaining code that uses the ORM-that-lost, and the Dates-library-we-don't-use-anymore, and it's OK.
