The UTF-8 encoded BOM is an offense to engineering.
Oh hey TIL why the UTF-8 byte order mark is the seemingly random byte sequence <EF BB BF>. It's simply because that's the UTF-8 encoding of U+FEFF, the code point that's also used as the byte order mark in UTF-16 and UTF-32.
UTF-8 has no issues with byte ordering, so the UTF-8 BOM is an oddity that shouldn't be emitted. But it exists and is specified because it's what happens if you take a BOM-ful UTF-16/32 sequence and naively transpose it to UTF-8, the leading U+FEFF BOM becomes <EF BB BF>.
Mozilla's CEO doubles down on them being an advertising company now.
tl;dr: "LOL get fucked"
They've decided who their customers are, and it's not you, it's people who build and invest in surveillance advertising networks. But in a "respectful" way....
https://jwz.org/b/ykaO
I used "crowdstrike" as a verb at work today, to paraphrase: "CI is broken because github crowdstruck us with a bad rust compiler update". AKA: usable any time an automatic update from a vendor breaks your infrastructure.
All I'm saying is, if they didn't want this neologism, they shouldn't have ruined my flight home from Italy.
can we not do the "weird" thing -_- there's nothing inherently wrong with being "weird", and lots of people who have been bullied or marginalized or oppressed are labelled "weird" in society and a lot of threat modelling is around "weird" people which tends to single out like people with mental illnesses, people of colour, disabled people, queer people, etc...
this isn't just an abstract "don't use problematic stuff" thing, leaning into the idea that "weirdos" are a threat and to be shamed is leaning into stuff that's already actively weaponized against lots of innocent people just living their lives, and no, this is not going to change the focus from them, it'll just reinforce the idea that "weird" is bad
also it's sad that "weird" resonates w/ people more than "fascist" :\
PSA: if you're in infosec red teaming an evil maid attack and you are not wearing a maid outfit while doing so, you may not be in full compliance with security standards and best practices
do remember that some industry regulators additionally require testing with cat ears for full certification. some organisations opt to further demonstrate protection against against the ‘moe moe kyun~’ blessing of a machine to auditors, but this is not currently mandatory under any scheme
"How does AI impact my job as a programmer?": https://chelseatroy.com/2024/05/26/how-does-ai-impact-my-job-as-a-programmer/
This is a brilliant piece told from the perspective of a Computer Science teacher.
It really hits in all the right places and mirrors a lot of my issues.
I appreciate the pragmatic approach of not fighting but letting folks see how it fails on interesting problems.
The article does not hesitant to point the finger back at the programming culture itself.