Deebster

I disagree, they have it working on the nRF52840 (which is new and supports new things like NFC and Thread/Zigbee). This means people can start developing features against that chipset.

Hardware doesn't mean "production-ready model".

I've coded in some esolangs, but never one that's nondeterministic - seems a nightmare! The design has the hottest paths most likely to degrade so I guess the idea is to have redundancy in your code?

The simple hello-world example is already 2002 lines long, so "production-ready" Furchtbar must be enormous.

This isn't a million miles from what bitcoin mining does, although in that case they're trying to find hashes that start with a lot of zeroes.

The uncropped version makes it a bit clearer:

It's also clearer that it's from an AI.

I just saw the top two thirds, and had to scroll to see the punchline and the comm - what a pleasant surprise! For me, it's the 3DO but that's too niche for most.

DFRA

That doesn't work, though.

For a recursive acronym, you want something like ADFRA Didn't Forget Recursive Acronyms.

Is this a joke? This is surely worse than using semvar.

It's a blue screen that's shown because something has died, I think it's a perfect fit.

I was going to post this myself, but you beat me to it. Great video.

date-fns? It's third in my search results but doesn't ring any bells to me.

I'll be very happy to not have to use Date any more. Pop quiz, what's in whatnum?

const vday = new Date('14 February 2025');
const whatnum = vday.getDay() - vday.getMonth();

Err, it's 5... Ha, amazing; that's not even the gotcha I meant to demonstrate. getDay returns the day of the week, the day of the month is returned from getDate.

Take two:

const vday = new Date('14 February 2025');
const whatnum = vday.getDate() - vday.getMonth();

So this is 14 - 2 = 12, right? Nope! The day (from getDate) is 1-based whereas month is 0-based, so 14 - 1 = 13.

Yeah, worth a read; it’s fun.

Rating: 1.5/5

That rating doesn't seem to match the rest of the review.