matzf

The "ass." more likely stands for "assuming".

Or use `chronic`.

Any particular reason for doing the human readable units "manually"? `du -h | sort -h` works just fine.

The Connect RPC protocol is pretty much that: https://connectrpc.com/docs/protocol

Sounds just like an episode of Black Mirror. About as creepy as it gets these days.

This reminds me of the similarly poetic output of git describe when no tags are available:

  $ git describe
  fatal: No names found, cannot describe anything.

That's no accident: from the Static CMS readme:

> Static CMS is a fork of Decap (previously Netlify CMS) focusing on the core product over adding massive, scope expanding, new features.

Such a prehistoric megastructure, a dyke to prevent the flooding of Doggerland in the North Sea, is the subject of the sci-fi novel "Stone Spring" by Stephen Baxter. This headline immediately reminded me of the book. I very much enjoyed reading this story and the two sequels, and I can fully recommend it!

> Originally 'quecca' had been suggested for 1030 but was too close to a profane meaning in Portuguese

(from https://iopscience.iop.org/article/10.1088/1681-7575/ac6afd, via wikipedia)

Seems like we missed opportunity to have an official metric fuckton.

Maybe we could use this approach to revive the n-gate instead. I'd enjoy their take on this idea.

> An imternet uses OpenAI (business model: "Uber for plagiarism") to help hacker news to incorrect eachother about a topic without having to read TFA.

No, the checksum just moves to UDP; in the current system, the UDP checksum is set to 0. This is not allowed in UDP/IPv6, where the checksum, calculated over both the IPv6 pseudo-header and the UDP payload, must usually be set.

A roundabout, then?

The huey project supports sqlite as one of its backend options (https://huey.readthedocs.io/en/latest/api.html#SqliteHuey). It works, is all I can say.

The openapi library seems to use requests incorrectly.

> If no authentication method is given with the auth argument, Requests will attempt to get the authentication credentials for the URL’s hostname from the user’s netrc file. The netrc file overrides raw HTTP authentication headers set with headers.

Source: https://docs.python-requests.org/en/latest/user/authenticati...

Explaining a joke ruins it, but as this has been voted down it seems necessary. This is a seemingly non-sensical quote from the song "If I had a million dollars" -- in the context of TFA it suddenly makes perfect sense. Chapeau!

Yes, it was supposed to be a reference to the show, glad you picked up on it.

Metal detectorists!

Ah no, oops, you had it right, force of habit ;)

So these ant-like cars were supposed to be more than just decoration?

From the article on the top balloon busting ace, Willy Coppens:

> Later when on another attack run, he got shot at from a balloon. He parked his plane on top of the damaged balloon, shut down his engine in order to protect its propeller, and waited until the balloon descended to slide off the balloon and fly away.

Rad!

Fair enough :) I just meant to point out what could go wrong.

Don't try this with C++, unless you're certain that there are no interdependencies or side-effects in global variable initialisation. The link order (usually) affects the order in which initialisers are executed.

This made my curious to find out. The "Language introduction" docs [1] answers these points;

* keys containing leading spaces, newlines or colons can be represented with the multiline key form, where each line of the key starts with `: `.

* leading or trailing space is not complicated; the string values are just the rest of the line after the separator from the key, `: `. The values are not trimmed.

* a string value beginning with `[` just works in most places. This would not be confused with list values, as these would only start after a new line. Only in the compact inline list and inline dict form there are restricted characters for syntax.

It seems that their claim, no escaping required, holds. The slightly more verbose form of the language constructs may be required to represent special values though.

[1]: https://nestedtext.org/en/stable/basic_syntax.html

This is not the point of the article, and maybe I'm just tired, but I'm confused; multiple paragraphs mention increased stack size with inlining:

> When a C compiler decides to not inline, there is likely a good reason. For example, inlining would reuse a register which require to save/restore the register value on the stack and so increase the stack memory usage or be less efficient.

> On the other side, the Py_NO_INLINE macro can be used to disable inlining. It is useful to reduce the stack memory usage.

This seems completely backwards, what are they talking about?

Ah yes, that's exactly what CRC32 is supposed to be used for. And it's even quicker if you don't compute it over the whole file, brilliant!

This already has the same problems as #2, but worse;this already has uneven distribution from the beginning, even without deletions. Perhaps it may be worth pointing this out: you mention that this creates a "perfect random distribution" but that "with only a few records the distribution is not as perfect". This is a misconception; this perceived imperfection, the clumps etc, that's what random points always look like. The size of the voronoi cells, which determine the probability of a point to be sampled, are of very different sizes here. What you are thinking of is a random distribution of points where the points will have somewhat uniform distance to their neighbors. This is called blue noise. Creating scattered points with blue noise properties in 2d is not very complicated, but it is a bit more complicated than just combining two uniform random values. FWIW, uniform randomness does not even have blue noise properties in 1d, perhaps much more obviously.

Anyway, if you had this blue noise, whether 1d or 2d, would still not solve your problem; once you start deleting points, you lose your beautiful properties of uniform voronoi cell sizes and your back to square one.

Yes, it does.

This is about corporate ethics. Just because these corporations happen to make use of computers doesn't make this a computer science issue.

Your articles are amazing, both very informative and entertaining! Thank you so much for researching and writing this! I have been checking your blog for updates regularly; please, do continue this series!

That's just a confusing name for boost::optional, right?