Re: Bubble go pop!
I wondered if by emissions you mean the planet destroying greenhouse gasses, or the never-ending torrent of AI slop, but your description adequately covers both.
4204 publicly visible posts • joined 6 Jun 2007
Exploiting a vulnerability on someone else’s computer is a violation of the UK's Computer Misuse Act (1990), and as AI is just a tool, the person using the tool is completely liable.
It is the users prerogative to sue the AI company if they feel they can prove the tool did not act in the way they expected, despite the AI company admitting it is unpredictable shit.
At least with a sewage farm it invokes some childhood memories of beach holidays in the 1970s*.
*I was walking through the village many years ago, when I thought I could smell the sea just like my family holidays in Devon in the 70s, then I came around the corner and found some road works with a warning sign for sewage works, I realised exactly what I'd been playing in as a child.
Not just travel typewriters, my dad brought home an ancient 1950s Remington from the office, when they upgraded to those new fangled electric golfball typewriters, it cast iron and weighed a ton, so definitely wasn't a travel model. That lacked both a 1 and a zero, 'l' and 'O' were considered close enough. That didn't matter for me as a child learning to bash the very heavy keys against a warn out ribbon.
I was very annoyed a few years later when home computer magazine started printing listings, and not all of them thought to use a font where 1 and l, 0 and O where indistinguishable.
Your points while having some validity don't address the problem - the Rustifiers aren't just not implementing certain functionality and giving an error if you try to use it - their versions accept the flags for the unimplemented features and SILENTLY ignoring them leading to incorrect results which aren't signalled to the caller.
It doesn't matter if you are a grey beard or not, whether C has ceased to exist and Rust isn't just a short lived fad until the next one-to-rule-them-all programming language comes along, or even if we just surrender the entire industry to AI, what the are doing is WRONG and dangerous.
There's one aspect of the project restart that will alienate some people, though: he is using AI. The Team section of the homepage says it's Maloney and Anthropic's Claude Code.
And everything sounded so good until that point.
"I get and understand the skepticism around AI people have, because I am not sure how much I trust AI-generated code myself, especially without review from humans. In my case, AI has always been more of an effort to accelerate my knowledge of what code does faster, versus not learning anything. With that said, I would still understand the reservations people would have in production environments."
Consider me reserved.
Somewhere, deep in the heart of Microsoft's Redmond campus, a sad-faced engineer is likely resetting the "Days since we broke something" counter and thinking fondly of the days when the number reached double or triple figures. ®
Except on Windows it's not days, but units of 18ms, and yes they managed triple digits of those once.
If they gain access to her email account, they can compromise any accounts which use email for a password reset.
Even if she doesn't have on-line accounts, email allows miscreants to sign her up for some, order credit cards, and run up debts.
Also don't forget the scams they can perform on her relatives should they be able to send and receive email which seem to be form her.
A few years ago I was working for a spin off of an F1 team, and we found that every other Friday something was buggering with our test rig. We knew the IP address, but not what the machine doing it was or where it was located, to be able to politely ask the owner to stop. I set off an nmap -A scan on the IP address and went off to lunch, only to return and find my colleague very perturbed as IT had come up from the depths of the basement wanting a stern word, thinking he was the culprit and not me. After explain to IT why I was doing it, both him and I were off the hook, and they helped us locate the rogue machine, which was actually a misconfigured strategists laptop in the pit garage track side, which explained why it only happed on the Friday of race weekends.
I have to regularly dip in to filing system rescue code I wrote over 26 years ago, and understand it quickly.
The way to do it is no matter how knowledgeable you are in the subject matter, write the code as if a clueless idiot has to maintain it.
Because in mere months, never mind years, of moving on to something else, you will be that clueless idiot, and there is no such thing as "that bit is so obvious I don't need to explain it".