Needs an endless repeating loop in there, plus one slang word spelled out in ridiculous furneticccc fashion, otherwise it’s just not Joyce. AIs just have no appreciation of great art.

time for brekkie again, bit of a walk, wanked off on the beach, got burrrrrluckesaaaid with a bunch of prozzies while me wife cucked me and back home in

Oh, one of our customers’ users deleted the /var directory on one of the servers we provided to them, because it was “taking up too much space on disk”. That’s where Postgres saves its DBs as well; wiped out weeks of work in production for them. This hits very close to home.

There’s three regions missing here - region 0 is “worldwide”, region 7 is “special purpose”, Oscar screening DVDs and the like, and region 8 is “international waters” for cruise ships and things. You can set several regions on the same disk, to make a 2/4/5 and the like. Set each region as a bit, and you can store that in a single byte - that makes it very easy to flash the firmware on DVD players to decide which disks they can play. Aus/NZ will want content in English and Latin America will want Spanish or Portuguese, so the DVD consortium can still get up to their often-illegal, certainly immoral, price fixing and bullshit.

Really, fuck DVDs. So much potential in the increased capacity, and then it was mired in crap like this and “disabled user operations” so that you can’t skip trailers. Time to raise the black flag and set sail for prosperous waters, me hearties.

The kernel option is mitigations=off, if you want to try adding it to your Grub command line? From the testing I’ve done, provides no benefits whatsoever - no more frames in games, compilation runs no quicker, battery life on a laptop is no better.

https://wiki.archlinux.org/title/Improving_performance#Turn_off_CPU_exploit_mitigations

If you made memory access lines twice as wide, they’d take up more space. More space means (a) chips run slower, because it takes time for the electricity to get there (b) they’d be bigger and more expensive.

The main problem with 32-bit, as others have noticed, is that that’s not really so much RAM. CPUs do addition and subtraction the way we were taught at school - ‘carry the one’, they’ve an overflow bit that’s set when your sum doesn’t fit in the columns. On 8-bit CPUs, we were always checking back when adding up large numbers. On 64-bit CPUs, we can deal with truly massive numbers anyway, it’s not such a hassle. And they’re so fast at doing sums anyway and usually waiting for memory, it’s barely a hassle.

Moving to 128-bit would give us a truly minuscule, probably unmeasurable, benefit in exchange for significant downsides. We could make them, but it would be pointless.

Yeah; as a native and fairly well-educated speaker, I’m fucked if I can form the past participles of some of our verbs

If I swim across a river, is it now the swimmed river? Swum river? Swam river?

If I sneak into a room, have I sneaked? Snuck? Both sound wrong.

Didn’t find anything ambiguous about ‘costed’, it works for me.