Ember do a good summary of their current trajectory:
> Australia’s largest source of clean electricity is solar (18%), which has doubled since 2020. Australia has the world’s highest solar generation per capita, over seven times the global average.
> Australia’s joint share of wind and solar (29%) is almost double the global average (15%), though it remains below peers like the United Kingdom (36%) and Spain (43%).
> Australia relied on fossil fuels for 65% of its electricity in 2024, with 46% coming from coal. Its power sector emissions have fallen by 21% from their peak in 2009 due to growth in solar and wind, even as demand has grown
We're using it with React and occasionally find the docs lacking (and go looking in the component source for the answers), but otherwise have been happy with it, fwiw :-)
One common suggestion is to not set Bash/shell options in the shebang because if someone runs the script with the interpreter explicitly (e.g. `bash my_script.sh`, rather than `./my_script.sh` (which, ime, is quite common as many people to seem to do it to avoid setting the execute bit, sometimes due to a lack of understanding ime)) then the options won't apply - which isn't fun...
Using `set` (e.g. `set -euo pipefail` as the first line after the shebang) is a common suggestion due to this, and similarly it helps with the `#!/usr/bin/env bash` case where the shebang can't handle additional arguments :-)
There are alternative C libraries that are worth considering, e.g. Zig (which is what Bun itself is written in, afaiu) supports using [musl](https://musl.libc.org) as an alternative to glibc, and musl can be statically linked as well (by contrast to the glibc quasi-static-linking).
We do - and have found it very reliable and I really like it :-)
One of the members of our team finds it more complex when it comes to diagnosing why things aren't running/starting as expected, but that's also down to the complexity we have around s6 with other setup scripts (we use it to manage the full suite of processes in our product).
Hence, they're not the biggest fan of it (and would talk negatively about it), but I _think_ s6 isn't really the culprit and instead the other complexity is.
Although, when things go wrong it can be a little bit harder to chase down than it was with our former manual "start this process" type scripts... But, you can just `./run` the run script which may tell you enough :-)
Thanks! That makes sense to me. Personally, I usually like tools and practices that can feel rough when there's too much complexity. When there are problems, I think it's generally good that people feel like there are problems.
OpenSSH also supports using a script to get the password if using the `SSH_ASKPASS` environment variable, and being invoked under a non-tty input e.g.
{ echo '#!/bin/sh' ; echo 'echo my_password' ; } > password.sh # don't do it like this :-p
chmod +x password.sh
SSH_ASKPASS=./password.sh DISPLAY= setsid ssh user@host /bin/id
In newer SSH versions `DISPLAY` is not required (but there is a new `SSH_ASKPASS_REQUIRE` environment variable), but in older (e.g. 8.x) versions, then it needs to be set as the default ssh-ask-password was an X11 command, and I believe the logic assumed that scenario.
> they get declined if your account is empty too AFAIK but haven't tested it ;P
Not always, at least some banks will allow you to go into overdraft and then charge a fee (e.g. $15 for Commbank) - so it's worth being cautious about running out.
I remember miscalculating and going into overdraft by a very small amount (e.g. a dollar or two) and then being slugged the overdraft fee - I would've much preferred the transaction to be declined, but that isn't/wasn't the default behaviour.
(No need to use bpftrace, just an easy example :-) )
reply