HN user

matzf

133 karma
Posts8
Comments28
View on HN

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.

Balloon Buster 3 years ago

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!

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?

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.

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!