Very well said. Reminds me of the old adage about /r/crypto “a place where people who don’t believe in financial regulations learn why financial regulations exist”
I would agree with you if we were in 1994 and this was about Rwanda.
Those tower blocks in Gaza that were felled on the anniversary of 9/11 were not taken down with machetes. We have got AI assisted targeting going on, with all of your favourite cloud service providers delivering value to their shareholders thanks to sales to the IDF.
The corporation that once had 'don't be evil' as their mission statement are suckling on the IDF teat along with Amazon, IBM, Microsoft and Cisco.
Israel: Surrender or we'll destroy your city
Hamas: Only if you let us rebuild and prepare the next war
Israel: Starts destroying the city by bombing emptied buildings, these having received warning from Israel beforehand
UN: Oh look, a genocide
This is politics and therefore probably off-topic for hn. It not being tech-related is irrelevant.
An argument could be made that it is an "interesting new phenomenon", but the post is most likely to result in tedious flamewars regardless and so should probably be killed.
> Off-Topic: Most stories about politics, or crime, or sports, or celebrities, unless they're evidence of some interesting new phenomenon. Videos of pratfalls or disasters, or cute animal pictures. If they'd cover it on TV news, it's probably off-topic.
I generally find HN discussions pretty interesting, but this particular topic seems to just be two groups who have zero chance of changing their minds hurling misinformation and propaganda at each other.
As a seasoned shell programmer, when I see set -euo pipefail, I know immediately that low quality code “batched list of commands”-type code follows.
It’s bad code smell and an anti-pattern as far as I’m concerned. Anyone who has actually has taken the time to learn POSIX/BASH shell to any degree or complexity knows that it’s fully capable of catching errors in-band and that a .sh file isn’t just a dumping ground for repeating your shell history.
> a .sh file isn’t just a dumping ground for repeating your shell history
Maybe it should be? As fun as it can be to write complex software in these legacy Turing tarpits, results aren't that great no matter how hard we try. Makefiles are another example.
reply