The article writer kind of complains that they’re having to serve a 10MB file, which is the result of the gzip compression. If that’s a problem, they could switch to bzip2. It’s available pretty much everywhere that gzip is available and it packs the 10GB down to 7506 bytes.

That’s not a typo. bzip2 is way better with highly redundant data.

It’s a bit vanilla but I like DejaVu Sans Mono 8pt in my terminal, which is where I edit scripts and things

Curiously, I don’t think that looks quite as good at larger sizes, so I’ve been using Liberation Mono 9pt or 10pt elsewhere.

Both of those have distinct glyphs for the usual easily confused candidates. Can’t be having my lowercase L’s and 1s looking similar.

You want a website and software that does Lemmy and Mastodon at the same time? That’d be kbin / mbin.

In part because of the kbin creator’s real world struggles, it hasn’t really taken off quite as well as Lemmy has, but its successor mbin is in use in a few places. I’m currently on fedia.io which is an mbin instance, for example.

Ehh. Old 8-bit machines had no trouble with the veritable Gordian knots written by kids in their bedrooms back in the day, so any chip’s gonna be fine.

That’s not to say this chip wouldn’t run it better…

Based on the positions of the "bonk"s and "ow"s, I posit that the target is a sentient floating torus.

Paired with the recent change that Oscar award judges are no longer allowed to skip parts of the media they’re reviewing (because apparently that was a thing), the number of AI slop movies is going to be absolutely gruelling for them to wade through.

One possible outcome is that this means AI kills the Oscars… but it’s more likely to get that watch-all rule rolled back.

And either way, it would probably mean that we’ll never see another 2001: A Space Odyssey again because a bunch of that movie looks like AI slop.

… I just realised this means that AI-generated movies could well end up being trained - accidentally or on purpose - to determine what would generate the most Oscars by exploiting underlying psychology that exists only in the sort of people who are employed as Oscar judges, but which somehow manages to mostly exclude everyone else.

That said, many people disagree with the Oscar nominations and awards anyway, so whether that makes any real difference is probably moot.

Henrietta Lacks hasn’t managed it yet. Look her up. It’s at least as bad as this if not more so.

“Yet” being the operative word here. There’s a disease in dogs that started in some very similar circumstances (although happening in nature rather than from a science accident). One slip-up from an immunocompromised tech with just the right genetic make-up and it begins.

If you approach people and tell them you’re normal, they won’t believe you. Something similar applies to saying you’re human on the Internet.

Hello, yes, I am a human.

Suspicious, isn’t it?

The cynic in me wants to know: Once purchased, will it, and any media it might contain at any time, be under the sole control of the purchaser?

If not, it’s definitely not worth buying.

For a certain set of inputs, yes. Good luck guessing what that comprises that set even if 1) there’s documentation and 2) you read it.

Worse, for all we know, double actually adds a thing to itself, which might accidentally or deliberately act on strings. Dividing by two has no such magic.

Perl was originally designed to carry on regardless, and that remains its blessing and curse, a bit like JavaScript which came later.

Unlike JavaScript, if you really want it to throw a warning or even bail out completely at compiling such constructs (at least some of the time, like this one) it’s pretty easy to turn that on rather than resort to an entirely different language.

use warnings; at the top of a program and it will punt a warning to STDERR as it carries merrily along.

Make that use warnings FATAL => "syntax"; and things that are technically valid but semantically weird like this will throw the error early and also prevent the program from running in the first place.

Well, you see, Perl’s length is only for strings and if you want the length of an array, you use @arrayname itself in scalar context.

Now, length happens to provide scalar context to its right hand side, so @arrayname already returns the required length. Unfortunately, at that point it hasn’t been processed by length yet, and length requires a string. And so, the length of the array is coerced to be a string and then the length of that string is returned.

A case of “don’t order fries if your meal already comes with them or you’ll end up with too many fries”.

As a Perl fossil I recognise this syntax as equivalent to if(not @myarray) which does the same thing. And here I was thinking Guido had deliberately aimed to avoid Perlisms in Python.

That said, the Perlism in question is the right* way to do it in Perl. The length operator does not do the expected thing on an array variable. (You get the length of the stringified length of the array. And a warning if those are enabled.)

* You can start a fight with modern Perl hackers with whether unless(@myarray) is better or just plain wrong, even if it works and is equivalent.

As far as people likely to say that middle one go, most of Britain would disagree that it rhymes with spider. You might get a crisp T or, more likely, a glottal stop, but not a D sound.

That said, Aussies are even more likely to use it and they do have some t-d merger going on in some of their accents.

Why the grimace? Rubber ducks definitely aren’t made of rubber these days. They’re plastic.

Nerd here. That’s soft-light Rimmer. He didn’t get the hard-light drive until they met Legion in season 6.

The only things he could physically interact until then were other holographic things provided by Holly or whatever his light bee was programmed to supply.

E-e-except where the script writers made a mistake. At one point he was able to smell something burning which definitely shouldn’t have been possible. Unless Holly simulated it for him anyway. That sort of shenanigan would be right up Holly’s alley now that I think about it.

(For the uninitiated, Holly is the sarcastic and dry witted AI in charge of supervising all ship computer operations. And he’s allegedly senile after 3 million years in deep space. Allegedly.)

Per screenshots of the “skeet” = As can be understood from screenshots of the post, also known as a “skeet”

as folks on the butterfly app = (a name that) users of Bluesky

are wont to call their posts… = like to call their posts…

“Skeet” being a combination of “sky” and “tweet”, which I hope you can figure out the origins of, and also a somewhat dirty word that the owners of Bluesky would really prefer people didn’t use as the non-generic name for posts on their platform, but is also disturbingly accurate if you compare the conceptually similar word “disseminate” for the spreading of information.

I should probably have separated the above into two sentences somewhere.

Old school gamer here. Headline should definitely say Quake II.

There might not seem to be much difference to a casual observer, but from that standpoint there’s not much difference between either and any other FPS. Even Minecraft to some extent.

Speaking of which, the Minecraft equivalent to this had all the same problems outlined in other comments here. Interesting as a proof of concept, but there are almost certainly better ways of using AI.

If endl is a function call and/or macro that magically knows the right line ending for whatever ultimately stores or reads the output stream, then, ugly though it is, endl is the right thing to use.

If a language or compiler automatically “do(es) the right thing” with \n as well, then check your local style guide. Is this your code? Do what you will. Is this for your company? Better to check what’s acceptable.

If you want to guarantee a Unix line ending use \012 instead. Or \cJ if your language is sufficiently warped.

I see I’ve forgotten to put on my head net today. You know the one. Looks like a volleyball net. C shape. Attaches at the back. Catches things that go woosh.