So I have a simple alternative to tying my shoes that you can teach and learn easily. Knots are all about the number of turns or wraps, so when tying your shoes instead of crossing the laces over once, do it twice. When you wrap around the loop, do that twice too. You may have to try it to understand, but it is easy and readily understandable to anyone who can already tie their shoes. The best part is the way you tighten it down and untie are are exactly the same as you have always done. It almost never comes untied, but still releases easily.

Sounds like that's still state of the art.

It helped improve my vim muscle memory substantially. Well done imo.

"This study systematically searched two databases and included six cohort studies included with limited types of digestive system cancers. Therefore, the evidence is not sufficiently strong to evaluate the relationship between digestive system cancers and plant-based diets. Comprehensive evaluations are scarce, especially for various digestive system cancers and multiple dietary patterns."

That eliminates the unused chain problem. Not sure if zig included that part of the feature as well.

Generally I agree though. The main problem with forcing unused variables, imo, is that it forces you to think a certain way. When I'm exploring the solution space on something, those constraints feel inhibiting.

I've been in a similar situation, where I created a relatively sophisticated A/* testing and control system. My idea of good use of the system ended up being very different from how the team employing the system thought about it.

I believe that is part of the point of the post, that unintended, and even unimagined side effects plague even the best of ideas.

Can someone confirm if there is some type of speed descent down from the Palisade Crest?

Update: it rerendered, now it looks like a rendering artifact (I hope).

The video is only one piece of the evidence. The pilots are trained, and other sensor systems confirmed what the camera was showing. This analysis is pretty flimsy.

The main feature of a uuid is it allows distributed generation. 32-bit or 64-bit integers are almost always sequential numbers. The sequential nature allows efficient page filling and index creation, but the contention involved in creating a sequence grows rapidly with scale.

So while a 128-bit uuid is larger than a 64 bit integer, this version allows for the bulk of the benefits of sequential integers while reducing the biggest drawback of contention at the point of creation.