TimeSquirrel

Me, the mystery dude in the game server who doesn't have a mic, doesn't use any voice features, never text chats, but always shows up and plays.

Wat? I can't hear you over the eeeeeeeEEEEEEEEeeEeeeEeeEEEEEEEEEEEEEEEEEEUUMMbumbumbumbumbumbumbumbumeeeeeeeeeeeeEEEEEEEEEEEEEEEEEE

No we obviously need more cheap plastics that will dry rot in your shed and shitty rubber grips that will turn to sticky goo in five years, as well as lowest bidder designed control circuitry with a dozen corners cut.

I get what you mean, modern power tools feel like Fisher Price toys. They're disposable.

What happened to the giant metal vacuum cleaners that doubled as a blunt-force weapons?

GitHub Copilot introduced a new keyword a little while ago, "@workspace", where it can see everything in your project. The code it generates uses all your own functions and variables in your libraries and it figures out how to use them correctly.

There was one time where I totally went "WTF", because it spat out Python. In a C++ project. But those kind of hallucinations are getting more and more rare. The more code you write, the better it gets. It really does become sort of like a "Copilot", sitting there coding alongside you. The mistake people make is assuming it's going to come up with ideas and algorithms for them without spending any mental energy at all.

I'm not trying to shill. I'm not a programmer by trade. Just a hobbyist who started on QBasic in the ancient times. But I've been trying to learn it off and on for the past 30 years, and I've never learned so much and had so much fun as in the last 1.5 with AI help. I can just think of stuff to do, and shit will just flow out now.

So your results are biased, because you're not going to see the decent programmers who are just using it to take mundane tasks off their back (like generating boilerplate functions) while staying in control of the logic. You're only ever going to catch the noobs trying to cheat without fully understanding what it is they're doing.

That would apply in my "encrypted container of some sort" solution, yes.

So let's stop calling it "deleted" then, and call it what it is. "Forgetting".

I'm not sure what you actually want the OS to do about it other than as I said, fill it with random data.

If every time an OS had to delete something it had to fill the space with zeros or garbage data multiple times just to make extra sure it's gone, we'd all be trashing our flash chips very fast, and performance would be heavily degraded. There really isn't a way around this.

The solution to keep private files private is to put them into an encrypted container of some sort where you control the keys.

What makes you think there’s no way of updating the firmware?

I don't know, but the amount of USB drives I've seen with a readily identifiable serial or jtag port and API documentation is exactly zero. 😉

I think most of them were one-and-done, as in, code/hardware was designed once, and never iterated on again, at least not for devices already in the field.

Wonder what the reason was for so much being in raw assembly when C existed. A basic library/API would be one of the first things I'd tackle in an OS. Move on to a higher level as soon as you're able.

That'd make it highly file system dependent with no way of updating the firmware. All these drives stopped working after the FAT32->ExFAT switch.