beagle3

How do you deal with the audio latency / missed packets / etc?

backtest on data collected after the day of release. Unless they have a time machine, or are themselves consuming the power you are measuring, it won't leak any data.

They are a (relatively) recent part of the production pipeline. Before introducing horseshoe crab blood, they used to inject rabbits and wait a couple of weeks. Now the wait has been reduced to minutes - which reduces storage costs and increases certainty.

But there are other options.

You expect every blog post to find the earliest relevant paper to cite, just so one could look at the year (without reading said paper - which would have made clear that the connection isn’t recent) to assess novelty? I don’t think that’s reasonable.

It’s a blog post. If it was, say, a peer reviewed paper by Hinton or LeCunn that fails to cite Schmidhuber, that would be reasonable criticism in my opinion. (Spoiler: they fail to cite him)

Same here. (Except, following 1980’s BASIC, I always expected it to be called “chain”)

At the same time they are strongly promoting the OS age laws.

One positive, in the eyes of many people, does not absolve for a large body of evil. For many it doesn’t even absolve a small body of evil deeds. (Zuck/Meta’s evil deeds are numerous and enormous)

It’s been years since, but I bought on Amazon a bag of 8 different ends that work everywhere in the world.

It wasn’t from Apple, but it’s basically a plastic shape and 2 or 3 (depending on end) metal parts - it’s hard to get wrong, and easy to test before use.

It’s been years since captcha was contributing to labeling.

That’s awesome. But a guide that does not include a howto for alerting (such as the one linked) is incomplete.

That’s comforting to know; that wasn’t true in the past for ext4 over lvm (is it true now?).

But what is that command? And how do you know which disk has gone bad?

I am sure I can get an answer from Google / Claude / ChatGPT, but a guide is incomplete without it - and the failure report should be active like a beep or flashing hardware light - I typically log into my NAS only a few times a year. A motd or other banner isn’t sufficient.

Indeed. Didn’t notice and it’s too late to edit now.

I still pay for snooty, and the reason for that is that when a disk goes bad (not if; when) I pop its tray out, replace the disk, pop the tray with the disk back in, click a couple of widgets, and that’s it. I know it will be rebuilt properly.

(And I know I have to do that, because when the disk fails it beeps and lights a led near the bad disk)

It’s easy to build a NAS such as the one described in this article, but in the long run, data loss is significantly more likely.

Also, any guide like this that doesn’t guide you through “disk 3 failed, this is how you safely replace it” is imho incomplete, even if it doesn’t go through telling you how you know a disk has failed.

What you seem to be saying is “I want no precedence or associativity - I just want explicit parentheses everywhere” which is a fine choice. But not a common one.

The reason APL made that choice (and its descendants followed) is that it had many tens of operators. There’s no intuitive or otherwise accepted order among them. Which means it’s either all parentheses (like you seem to prefer) or a simple rule (left-of-right). There’s basically no other solution.

Forth and Lisp also dropped precedence and associativity rules, each in their own way.

APL / K / J (and friends) evaluate things "left-of-right" (could be thought of as "right-to-left"), that is 1+23-4 is parsed 1+(2(3-4)) - there is no operator precedence. It is weird at first, but refreshingly simple and effective once you manage to overcome indoctrination you received since elementary school.

My guess would be because too many users held out with Win10, are not really a potential income stream, and MS would rather keep them MS customers than Linux or Mac (their next machine might be a Neo rather than Win11 these days).

The cost to Microsoft is essentially zero if they ate already committed to these security updates (and they are, at least for the LTSC branch and some government contracts)