LE by default successfully ran 2 months prior. 2 months and 5 years are two completely different worlds in terms of bit rot. That and there are many generic tutorials and scripts and knowledgeable devs for configuring LE fresh.
It's all just theories. But yes the article is basically summarizing a new paper/model. Most likely: the model is incorrect in some ways. But maybe useful in others.
I mean yeah that's basically what high compression solutions like paq have done, depending on the compression level desired apply increasingly speculative and computationally intensive models to the block and pick whichever one worked the best.
C has some of the best static analysis and debugging tools of any language, but all of that's worthless if you don't use them. Doubly so if you specifically handicap those tools and write your own obfuscated allocation scheme. Heartbleed was less an indictment against C and more an indictment against shitty code.
Worse, overwriting SSD's with random data would halve their lifespan, and some SSD's don't even allow you to control where exactly you are writing to. Better to just never write unencrypted data to the drive at all.
It's not a bug. This is how you display that there's no road there right now (unless you are working on construction). Likely this is a pretty good representation of the information available for pathfinding as well.
Browser equivalence is another thing entirely. Most browsers will accept http://www。google。com (because in Japanese '。' is '.'). But if you tried to request that actual resource it doesn't lead anywhere.
Even better, you can demonstrate the effect pretty easily. Jog alongside a bike and let it go. If it's fast enough, it will stay upright. You can even try to kick it over and the front wheel will turn towards the direction the bike is falling, "catching" the bike and converting the fall into a turn.