:x is also an alternative to save and quit.

Equally valid for the facial expression you’d make upon finding that out.

Both, of course.

Cloudflare’s is a corporate solution from the company that man-in-the-middles half the internet and makes me click shit every fucking time. I see it whenever I make the mistake of following a stackoverflow link.

It is also not very useful if you don’t use a PC. Every time I look up a Cloudflare-gated site on my iPad, I usually have to jump through a few captchas before it will let me in, if it doesn’t decide to be a grump and decide to put you in a sisyphean cycle of captchas, constantly refreshing without end.

Or if you use some software. I have citation software that gets stuck in the loop because Elsevier puts their journals behind a Cloudflare wall, and when it pops up the prompt to prove you’re not a bot, just refreshes straight into another prompt.

Yes, but in this case, you can see what the model is doing, and it is running on your actual computer. Whereas a lot of LLM providers tend to run their models on their own server farms today, partly because it’s prohibitively expensive to run a big model on your machine (Deepseek’s famous R1 model needs at least a hundred GBs of VRAM, or about 20 GPUs) and partly so that they have more control over the thing.

AI isn’t a black box in the sense that it is a mystery machine that could do anything. It’s a black box in the sense that we don’t know exactly how it’s working, with which particular probability vector/tensor is responsible for what, though we have a fairly good general idea of what goes on.

It’s like a brain in that sense. We don’t know which exact nerve-circuits do what, but we have a fairly good general idea of how brains work. We don’t think that if we talk to someone, they’re transmitting everything you say to the hivemind, because brains can’t do that.

Getting it to format documentation for you seems to work a treat. Nothing too complex, just “move this bit here, split that into points”.

Trying to monetize the piracy of your users. That’s a bold business strategy.

Some time ago, never mind how long precisely, Plex were trying to legitimise themselves, by adding streaming from official sources, etc.

I would be curious if this is meant to be a deterrent, or just to look like one by making piracy expensive, so they can eat their cake and have it too.

Pragmatically, is that really any different with a passcode? Someone might not be able to physically force an unlock like with biometrics by moving the relevant body part over, but there’s certainly nothing stopping someone from forcing you to unlock your phone if you had a passcode through by duress. Most thieves would have certainly wised up enough to force you to remove your passcode before leaving, or they’d watch you unlock your phone, and figured out the passcode that way.

I rather doubt that, if in that kind of situation, there would be many who would resist. Your phone is not worth your life for most.

Personally, if I wasn’t doing anything sensitive, like travelling through some countries (like Australia/the US) or going to a protest, I’d probably keep it on. The convenience makes up for it for the most part.

The glass is also speaking, as opposed to a third person.

Yes, was poking fun at Ed’s only error message being a relatively unhelpful ?.

?

It’s also self explanatory, which is great if you’re new.

Ed and Vim are basically arcane by comparison.

Does it count as user error if the user has to micromanage the compiler?

?

Out of memory/overheating in 60k rows? I’ve had a few multi-million row databases that could fit into a few gigs of memory, and most modern machines have that much in RAM. A 60k query that overheats the machine might only happen if you’re doing something weird with joins.

Plus a lot of reads is nothing really, for basically all databases, unless you’re doing an unsmart thing with how you’re reading it (like scanning the whole database over and over). If you’re not processing the data, it’d be I/O bottlenecked.

“Software Engineer” was literally right next to it.

If they went into uni straight out of high school, they could. A lot of Bachelor holders would be around that age, since they start at 18.

Hard Drives might do it if the enclosure is poorly designed (no ventilation), but I can’t imagine a situation where it would overheat like that that quickly, even in a sealed box. 30k is nothing in database terms, and if their query was that heavy, it would bottleneck on the CPU, and barely heat the drive at all.

Unless the database was designed by someone who only knows of data as that robot from Star Trek, most would be absolutely fine with 60k rows. I wouldn’t be surprised if the machine they’re using caches that much in RAM alone.

Unless they actually mean the hard drive, and not the computer. I’ve definitely had a cheap enclosure overheat and drop out on me before when trying to seek the drive a bunch, although it’s more likely the enclosure’s own electronics overheating. Unless their query was rubbish, a simple database scan/search like that should be fast, and not demanding in the slightest. Doubly so if it’s dedicated, and not using some embedded thing like SQLite. A few dozen thousand queries should be basically nothing.

Not quite that, but more the ${variable##.*} sort of thing.