There is a token you must pass around, sure, but because you use the same token for both async and sync code, I think analogizing with the typical async function color problem is incorrect.
I don't appreciate these kinds of simple one-line referential jokes on HN, but your joke was to emulate perfectly the central issue of TFA, so I do agree that it brings into question who did and who did not read the article -- I know you read it.
I think it was a good enough joke or witty remark grounded in the crux of the article that it’s worth it. And it’s certainly interesting to see the “whoosh” past many of the commenters
It's not about the "age" of the number at all, devices are mandated to try all available networks when it is a recognized emergency number. In this case, even though the number was indeed a device-recognized emergency number, it failed to try all available networks as mandated. The article mentions Triple Zero several times, but not because that is specifically noteworthy beyond it being the typical emergency number.
I don't take anything Leon Panetta says as gospel, but the fact that someone like him says this shows how the position is not ludicrous in the way you and other similar replies are painting it.
Most programmers don't prefer thread local mutable state over a single pointer argument. Especially for general purpose code (i.e., not specific to a single purpose/project). With the mutable state version, you have to clearly define which state you're using and when (which named allocator/arena variable), and if you're mutating it in place and then restoring it, there can be some pretty obvious issues.
Given this thread is completely off the rails from anything specific to allocators or arenas, and even Zig, I will now exit.
I have read up on the law. They have no reason to worry and even if they did, given the extent of non-compliance in the porn industry, they are so far down the pecking order that this reaction looks like what it is: activist narcissism.
Wow, this is much faster and higher quality than the meloTTS program I was using before, and has many more voices available... although it doesn't appear to support Japanese.
You can make this app yourself in an hour if you're on Linux and can do some scripting. Mockup below for illustration, but this is the beating heart of a real script:
# whisper-live.sh: run once and it listens (blocking), run again and it stops listening.
if ! test -f whisper.quit ; then
touch whisper.quit
notify-send -a whisper "listening"
m="/usr/share/whisper.cpp-model-tiny.en-q5_1/ggml-tiny.en-q5_1.bin"
txt="$(ffmpeg -hide_banner -loglevel -8 -f pulse -i default -f wav pipe:1 < whisper.quit \
| whisper-cli -np -m "$m" -f - -otxt -sns 2>/dev/null \
| tr \\n " " | sed -e 's/^\s*//' -e 's/\s\s*$//')"
rm -f whisper.quit
notify-send -a whisper "done listening"
printf %s "$txt" | wtype -
else
printf %s q > whisper.quit
fi
You can trivially modify it to use wl-copy to copy to clipboard instead, if you prefer that over immediately sending the text to the current window. I set up sway to run a script like this on $mod+Shift+w so it can be done one-handed -- not push to listen, but the script itself toggles listen state on each invocation, so push once to start, again to stop.
reply