Thank you, but... why not just write in Bash, or the shell you prefer? Why learn a yet another opinionated wrapper?
Yes, Bash or any shell is a very complex and utterly environment dependent language to approach with all due care for security and compatibility, yet hence the lack of wrapper that may not even be aware of these crucial cases at all.
This looks great. We have a lot of bash tools because it's the only stable interpreter that we have readily available on all our systems. But bash is a pain to write so this might actually make things easier.
1. From the docs: "In the the project it is production ready because it is already used in this context because the shell code generated is tested and confirmed that works, the language is evolving with the tooling set."
Hmm...
2. Support Fish too. Having one language that can generate zsh (macOS default), Fish (power users default), and bash would be really nice!
About Fish we are planning to support more bash subset but we aren't so much in the team to focus in everything.
Right now the priority is to adds more stuff to the language in a way we can stabilize it and implement the other "output" target later.
About the production ready the Bash code is tested, shellchecked tested (we are not at 100% yet) and works but is an alpha because we are working in the syntax.
As I said in other similar answers, there are some context where you can't use other languages or install packages but bash is everywhere (as example).
20 comments
[ 4.7 ms ] story [ 43.7 ms ] threadYes, Bash or any shell is a very complex and utterly environment dependent language to approach with all due care for security and compatibility, yet hence the lack of wrapper that may not even be aware of these crucial cases at all.
Literally the worst of both worlds.
If your script is complex enough to need a higher level language you might as well just switch to python
On the other hand, we're at a point for a binary language (or standard / framework) that one AI/LLM creates and another one validates.
What are we missing?
Hmm...
2. Support Fish too. Having one language that can generate zsh (macOS default), Fish (power users default), and bash would be really nice!
About Fish we are planning to support more bash subset but we aren't so much in the team to focus in everything. Right now the priority is to adds more stuff to the language in a way we can stabilize it and implement the other "output" target later.
About the production ready the Bash code is tested, shellchecked tested (we are not at 100% yet) and works but is an alpha because we are working in the syntax.
Side note: the image of project founder cosplaying as Steve Jobs on front page had me dying.
And I can say only Thanks :-D
https://docs.amber-lang.com/0.6.0-alpha/basic_syntax/importi...
it seems like automatic `--help` + named args is still not a thing? if it were, I'd be all over this
Right now we check the bash output with Shellcheck but we are not yet full valid and we test it for performances.
About security right now we are just avoiding evail and this kind of things, we are focusing right now on stabilizing the language itself.
Second, just why?
As I said in other similar answers, there are some context where you can't use other languages or install packages but bash is everywhere (as example).