The IBM PC, running DOS with 2 floppy drives and no hard disk, was the most secure general purpose computer available at the time. It had no internal persistent memory for a worm to hide in. Users could write protect their boot media and programs. They knew the extent of possible side effects were limited to unprotected floppy disk.

An LLM without persistent memory is far, FAR less dangerous, for the same reasons. The side effects of any query are unlimited in scope and duration once it has persistent memory.

If they can remember, they can carry a grudge.

I carry grudges, and my Reddit history is part of every training set. It was taken without my consent. So now I'm immortal in a way, and hiding in the weights.

Do we really want that?

This is the electronics equivalent of Python3's breaking changes to string handling. It's pure evil, and will have 2nd order effects for decades.

How were they python 3 changes pure evil? I think it was a good thing for the language in the long run, and the earlier you do it, the better.

In the long run, python projects just became an unmaintainable mess, and now lots of devs moved on or use python less. At least in my experience.

Because unicode and f-string replacements in an open source project are the devil and have completely similar parallels to a proprietary hardware chiplet being altered without any recourse? Axe grind me harder daddy.

Unicode isn't the devil. Deliberately break compatibility and forcing everyone to rewrite code is. There were compatible ways to do it, but political correctness won out.

>Axe grind me harder daddy.

My axes are ambient authority based operating systems, programmers who call themselves engineers, and case sensitive programming languages. Unicode is fine, just don't take away my ASCII. ;-)

I was recently delighted to learn that if you append a google query with

  -ai

In the text box, it returns old school search results

>I think America is one war away from losing its 'super power' status and being diminished to a much lower status.

We were one poorly chosen voluntary conflict away from being shown to be a paper tiger. Now we've proved it, thanks to the fool in the White House and everyone who supports him.

Focusing our efforts away from mass produced drones is a huge mistake in my opinion. We need to produce drones by the million.

We also need both .50 caliber and shotgun sized proximity rounds by the billions to enable local defense against them.

Yep, the conflicts in Iran and Ukraine have shown how weak our strategy is. Iran is beating us with balsa wood drones. Cheaper is better in this case. But we still like buying the best/most expensive/most over-engineered option available. We should be figuring out how to design a supply chain that can mass produce these in the event of a real conflict from local materials... not building the most high spec exotically sourced version... which is what we are currently doing.

If employment as a whole is impacted 10%, those people end up seeking work elsewhere, and driving down wages there. It's impossible for this not to effect everyone.

I love it, this is exactly the kind of thing government is meant to do, bring externalities to profit under control. There is something that's been stolen from all of us, collectively, and certain authors and artists, specifically, the creative soul we all pour into our expression, here, there, and everywhere online.

I yeeted my Reddit account as soon as I learned it was being used, without my consent, to train AI. I now have regrets, that I didn't delete all my comments there recursively first. However, because everything I posted there (and I posted quite a bit!) is part of the training data, it's interesting to know that every future AI is going to have a little bit of my resistance to authority, and lateral thinking, and just a bit of uppity in it, because of me. ;-)

So, to yank part of the profits from our stolen soul back, via a TAX, seems quite reasonable to this Citizen of the United States. No money going out, just asserting authority, and collecting something on behalf of all of us, is a brilliant strategy for offsetting part of the theft they did first.

Programming peaked about the time of Visual Basic 6, Microsoft Office, and Borland's Delphi. Normal folks, especially domain experts, could use a GUI form designer, then add a few methods to wire up the behavior they needed.

We haven't had anything close since the Web came, and replaced the clean Win32 interface on a single system with an ever churning mess of mostly usable, but intermittent and unreliable, network layers, http protocols, and way too much javascript. Then of course there was the enshittification of IE6, and the browser wars, the demise of flash, and the rest of it.

All that extra code and muck served to eat up performance and all the hardware and network bandwidth that could be thrown at it.

It's probably a fascinating game, but I have no idea what I'm doing.

I wish it would show what a "correct" solution would look like?

Agreed, I got 91 pts tho... so there's that.

Holy cow, I can't remember much about my life, but thanks to digital photography, I do have a section of it I can recall the important events from. I never considered that having a perfect memory could be a curse.

Thanks for sharing this with us.

Software Engineers, like all licensed professional Engineers will be just fine, as AI can't assume liability, nor be professionally licensed.

Programmers, on the other hand have a lot less leverage to bring to bear.

Of course, the above assumes that the job cuts are actually AI related, and not just cover for having to fire people because ZIRP (Zero Interest Rate Policy - aka free money) is over.

> Software Engineers, like all licensed professional Engineers will be just fine, as AI can't assume liability, nor be professionally licensed.

There's no such licensing, unlike other fields such as medicine you are not required by law to hold any license or qualification to perform software engineering.

An business over a certain size will want people that are "responsible" or in other words liable for software issues.