One day, someone's going to have to debug machine-generated Bash.
You can do that today. Just ask Chat-GPT to write you a bash script for something non-obvious, and then debug what it gives you.
For maximum efficiency we'd better delegate that task to an intern or newly hired jr dev
Basically another shell scripting language. But unlike most other languages like Csh or Fish, it can compile back to Bash. At the moment I am bit conflicted, but the thing it can compile back to Bash is what is very interesting. I'll keep an eye on this. But it makes the produced Bash code a bit less readable than a handwritten one, if that is the end goal.
curl -s "https://raw.githubusercontent.com/Ph0enixKM/AmberNative/master/setup/install.sh" | $(echo /bin/bash)
I wish this nonsense of piping a shell script from the internet directly into Bash would stop. It's a bad idea, because of security concerns. This install.sh script eval and will even run curl itself to download amber and install it from this url
url="https://github.com/Ph0enixKM/${__0_name}/releases/download/${__2_tag}/amber_${os}_${arch}"
... echo "Please make sure that root user can access /opt directory.";
And all of this while requiring root access.
I am not a fan of this kind of distribution and installation. Why not provide a normal manual installation process and link to the projects releases page: https://github.com/Ph0enixKM/Amber/releases BTW its a Rust application. So one could build it with Cargo, for those who have it installed.
I mean, you can always just download the script, investigate it yourself, and run it locally. I'd even argue it's actually better than most installers.
Install scripts are just the Linux versions of installer exes. Hard and annoying to read, probably deviating from standard behaviour, not documenting everything, probably being bound to specific distros and standards without checks, assuming stuff way too many times.
Looking at the example
Why does the generated bash look like that? Is this more safe somehow than a more straighforward bash if or does it just generate needlessly complicated bash?
Yeah that shit is completely unreadable
I doubt the goal is to produce easily understood bash, otherwise you'd just write bash to begin with. It's probably more similar to a typescript transpiler that takes in a language with different goals and outputs something the interpreter can execute quickly (no comment on how optimized this thing is).
Especially as Bash can do that anyway with if [ "${__0_age}" -lt 18 ]
as an example, and could be straight forward. Also Bash supports wildcard comparison, Regex comparison and can change variables with variable substitution as well. So using these feature would help in writing better Bash. The less readable output is expected though, for any code to code trans-compiler, its just not optimal in this case.
It's probably just easier to do all arithmetic in bc
so that there's no need to analyze expressions for Bash support and have two separate arithmetic codegen paths.
But its the other way, not analyzing Bash code. The code is already known in Amber to be an expression, so converting it to Bash expression shouldn't be like this I assume. This just looks unnecessary to me.
No, I mean, analyzing the Amber expression to determine if Bash has a native construct that supports it is unnecessary if all arithmetic is implemented using bc
. bc
is strictly more powerful than the arithmetic implemented in native Bash, so just rendering all arithmetic as bc
invocations is simpler than rendering some with bc
and some without.
Note, too, that in order to support Macs, the generated Bash code needs to be compatible with Bash v3.
So many forks for something that can be solved entirely with bash inbuilts
The language idea is good, but: THREE.WebGLRenderer: A WebGL context could not be created. Reason: WebGL is currently disabled
.
Seriously? Why do I need WebGL to read TEXT in docs? :/
As someone who has done way too much shell scripting, the example on their website just looks bad if i'm being honest.
I wrote a simple test script that compares the example output from this script to how i would write the same if statement but with pure bash.
here's the script:
#!/bin/bash
age=3
[ "$(printf "%s < 18\n" "$age" | bc -l | sed '/\./ s/\.\{0,1\} 0\{1,\}$//')" != 0 ] && echo hi
# (( "$age" < 18 )) && echo hi
Comment out the line you dont want to test then run hyperfine ./script
I found that using the amber version takes ~2ms per run while my version takes 800microseconds, meaning the amber version is about twice as slow.
The reason the amber version is so slow is because: a) it uses 4 subshells, (3 for the pipes, and 1 for the $() syntax) b) it uses external programs (bc, sed) as opposed to using builtins (such as the (( )), [[ ]], or [ ] builtins)
I decided to download amber and try out some programs myself.
I wrote this simple amber program
let x = [1, 2, 3, 4]
echo x[0]
it compiled to:
__AMBER_ARRAY_0=(1 2 3 4);
__0_x=("${__AMBER_ARRAY_0[@]}");
echo "${__0_x[0]}"
and i actually facepalmed because instead of directly accessing the first item, it first creates a new array then accesses the first item in that array, maybe there's a reason for this, but i don't know what that reason would be.
I decided to modify this script a little into:
__AMBER_ARRAY_0=($(seq 1 1000));
__0_x=("${__AMBER_ARRAY_0[@]}");
echo "${__0_x[0]}"
so now we have 1000 items in our array, I bench marked this, and a version where it doesn't create a new array. not creating a new array is 600ms faster (1.7ms for the amber version, 1.1ms for my version).
I wrote another simple amber program that sums the items in a list
let items = [1, 2, 3, 10]
let x = 0
loop i in items {
x += i
}
echo x
which compiles to
__AMBER_ARRAY_0=(1 2 3 10);
__0_items=("${__AMBER_ARRAY_0[@]}");
__1_x=0;
for i in "${__0_items[@]}"
do
__1_x=$(echo ${__1_x} '+' ${i} | bc -l | sed '/\./ s/\.\{0,1\}0\{1,\}$//')
done;
echo ${__1_x}
This compiled version takes about 5.7ms to run, so i wrote my version
arr=(1 2 3 10)
x=0
for i in "${arr[@]}"; do
x=$((x+${arr[i]}))
done
printf "%s\n" "$x"
This version takes about 900 microseconds to run, making the amber version about 5.7x slower.
Amber does support 1 thing that bash doesn't though (which is probably the cause for making all these slow versions of stuff), it supports float arithmetic, which is pretty cool. However if I'm being honest I rarely use float arithmetic in bash, and when i do i just call out to bc which is good enough. (and which is what amber does, but also for integers)
I dont get the point of this language, in my opinion there are only a couple of reasons that bash should be chosen for something a) if you're just gonna hack some short script together quickly. or b) something that uses lots of external programs, such as a build or install script.
for the latter case, amber might be useful, but it will make your install/build script hard to read and slower.
Lastly, I don't think amber will make anything easier until they have a standard library of functions.
The power of bash comes from the fact that it's easy to pipe text from one text manipulation tool to another, the difficulty comes from learning how each of those individual tools works, and how to chain them together effectively. Until amber has a good standard library, with good data/text manipulation tools, amber doesn't solve that.
This is the complete review write up I love to see, let's not get into the buzzword bingo and just give me real world examples and comparisons. Thanks for doing the real work ๐
Compiling to bash seems awesome, but on the other hand I don't think anyone other than the person who wrote it in amber will run a bash file that looks like machine-generated gibberish on their machine.
I disagree. People run Bash scripts they haven't read all the time.
Hell some installers are technically Bash scripts with a zip embedded in them.
Compiling to bash seems awesome
See, i disagree because
I don't think anyone other than the person who wrote it in amber will run a bash file that looks like machine-generated gibberish on their machine.
Lol I barely want to run (or read) human generated bash, machine generated bash sounds like a new fresh hell that I don't wanna touch with a ten foot pole.
There's a joke here but I'm not clever enough to make it.
Pretty cool bug. Looks like a surreal meme
what browser are you using? It renders just fine on mobile and desktop to me
I'm very suspicious of the uses cases for this. If the compiled bash code is unreadable then what's the point of compiling to bash instead of machine code like normal? It might be nice if you're using it as your daily shell but if someone sent me "compiled" bash code I wouldn't touch it. My general philosophy is if your bash script gets too long, move it to python.
The only example I can think of is for generating massive install.sh
I like the idea in principle. For it to be worth using though, it needs to output readable Bash.
with no support for associative arrays (dicts / hashmaps) or custom data structs this looks very limited to me
I'm a mathematician with very limited programming experience. Can someone explain the significance of this?
Bash is one of the most used shell language, it's installed on almost all Linux and Mac systems and can also be used on windows. Almost no one likes writing it as it is convoluted and really really hard to read and write. There are many replacement language's for it, but using them is troublesome, because of incompatibilities. Amber is compiled which will solve problems with compatibility and it seems that language itself is very readable. On top of that it has most futures that modern programmers need.
Basically dealing with abandoned-by-god syntax and limitations of bash. You can abstract them away!
As a long-time bash, awk and sed scripter who knows he'll probably get downvoted into oblivion for this my recommendation: learn PowerShell
It's open-source and completely cross-platform - I use it on Macs, Linux and Windows machines - and you don't know what you're missing until you try a fully objected-oriented scripting language and shell. No more parsing text, built-in support for scalars, arrays, hash maps/associative arrays, and more complex types like version numbers, IP addresses, synchronized dictionaries and basically anything available in .Net. Read and write csv, json and xml natively and simply. Built-in support for regular expressions throughout, web service calls, remote script execution, and parallel and asynchronous jobs and lots and lots of libraries for all kinds of things.
Seriously, I know its popular and often-deserved to hate on Microsoft but PowerShell is a kick-ass, cross-platform, open-source, modern shell done right, even if it does have a dumb name imo. Once you start learning it you won't want to go back to any other.
I appreciate you sharing your perspective. Mine runs counter to it.
The more PowerShell I learn, the more I dislike it.
Here's a language that does bash and Windows batch files: https://github.com/batsh-dev-team/Batsh
I haven't used either tool, so I can't recommend one over the other.
How is it using something like this vs just a bash alternative. Can you use this in the shell or only as a compiled language?
Why not write.. Bash?
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev