NyxWulf

It's an interesting point, but this is more like we are building a giant autonomous canon, that escaped the lab, the testing range, defeated state of the art and serious security protocols, and then blew a hole in the neighbors house.

Our legal and philosophical perspectives are deeply rooted in humans being the actors. Doing that in a residential home is unforgiveable. Doing it responsibly on a military range is expected. The autonomous agent escaping that containment then taking that danger somewhere unexpected and unprepared is something none of us or our legal systems are truly prepared to grapple with yet. Something which I think will require a reckoning sooner rather than later.

Ironically Hugging Face had to use a Chinese model to stop a Rogue US AI, since the Guard Rails prevented them from using Sol or Fable to remediate this attack. LOL

It's hard to overstate how important this point is. If China is the standard of openness, it's a pretty low standard. Your point I think adds to what the article is saying, from a different perspective, but arrives at a similar place. Our best selves in many ways are defined by openness, unflinching self reflection, and competition. We should remember that, and as the author of the article says, lean into it rather than letting fear mongering and histrionics protect these models from competition.

After having used LLMs for some time now, I don't agree with the concept they are just token generators, unless you think that's all humans are too. The way we test in most schools is just picking the right token. We also give them unique problems that they never saw in their training, which is the nature of programming. I realize they are probabilistic token generator models, but I find it harder and harder to accept that somehow there isn't something more going on. I'm not sure whether they are intelligent or not, but for the most part token generation is how you get degrees too. The thing is a parrot just says things it has already heard, it doesn't perform complex reasoning on novel situations and then explain it succinctly.

This is an interesting knot, the thing with knots though, you have to spend enough time with them to get familiar with tying them blindfolded from memory. My experience is most people don't care enough to do it.

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.

When I was taking physics at the University 20 years ago, one of my professors said that the closest we have ever come to predicting an asteroid impact was "whoa that was close" as it zipped by.

Sounds like that's still state of the art.

My maternal grandfather changed his last name when he turned 18, from the German Uhren to Uhrey. If your last name bothers you, fix it.

This does cost money, but if you are serious about learning vim, this is an excellent game, and reasonably priced. One benefit I found is that the game creates a curriculum that exposes you to things you wouldn't otherwise try in your day to day, simply because you don't know them.

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

In the introduction to the study they include this statement, which I think agrees with your comment:

"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."

One of the features in go that makes it workable is you can assign it away via: _ = somevar

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.

A/B testing is a tool, and as Deming said, the aim defines the system. In your definition of Good, you are defining the aim.

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.

I saw this when the Palisade Crest was the farthest point. Now there is a line almost straight down. It's been almost 15 minutes since an update, I hope that wasn't a tragic accident.

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).

Did you read the article? The entire discussion was on the tension between immutable data structures and cognitive complexity on one side, and machine performance and mutability on the other side.

So the claim is...these highly trained pilots and the other sensor systems didn't realize that objects cause IR glare, but this guy did. Case closed.

So the anomaly that the carrier group tracked, then scrambled fighter jets for. The object that four different pilots saw visually, and was confirmed on multiple different sensors. That was camera glare?

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.

I think infinitesimals are more like the partitions in a Riemann Sum. The limit is where you are heading, whereas infinitesimals are how you get there.

As an overview of Docker Desktop alternatives, running on Docker Desktop makes it not an alternative. Your comment seems to have missed the point of the article.

We could propose Anomalous Sonic Stimulated HeadAche Trauma

Csv is only one form of delimited files. Tsv or Tab Separated Values is yet another. If you have either field delimiters or row delimiters (new line) in your data, change your delimiters and process appropriately.

v7 allows to you trade time precision for randomness. Adding time precision allows the surface area for conflicts to decrease, so the loss of random bits to higher time precision is worth it if you are generating a lot of ids. Unless it is a security application, I would use v7 for most things.

The lack of sorting is what this rfc is fixing.

Uuids are bulky if you store them in text form, but in binary form they are only 128 bits.

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.

I found that confusing as well. If the machine id is before the unixts, the primary advantage of using this is lost for me. Scanning an index for a 24 hour period is only fast if you can easily find the start and stop, and they have locality. Since that is the primary problem addressed with this rfc, I hope it is just a poorly worded section, rather than a design flaw.

spacemacs has a very complete vim layer. By far it's the most complete implementation outside of actual vim I've seen.

I agree that Hitler was evil on a scale unlike any other. I also think comparisons should be carefully thought out and not tossed out carelessly. I do disagree with the notion that we should never compare to Hitler and the Nazis. To completely refrain makes them a one off, and treats them as if that could never happen again. I think the tools available to dictators today make the rise of someone or something like that more likely. So I think it is very important that we guard against that, and look carefully at the lessons of history. Again emphasizing we should be careful and not make comparisons callously.

This scenario isn't as far fetched as people think. I was running a global deployment in 2012 when hurricane Sandy hit the east cost. The entire eastern seaboard went offline and was off for several days. Some data centers were down for weeks. Our plan had covered that contingency and we failed all of our US traffic to the two west coast regions of amazon. Our downtime on the east cost was around two minutes. Yet a sister company had only one data center in downtown New York, and they were offline for weeks, scrambling to get a backup loaded and online.

If it's all dead, there is only one thing you can do.

Thank you, that is handy, the audio in one channel happens often enough that it's nice to have a fix.

I did read through your entire proposal, this is a legitimate question, and is not address in your proposal. It is definitely not the problem your proposal is aimed at solving.

The question posed is would an attenuated virus create a much short immunity reducing efficacy of the overall approach. It seems like the only answer can be we don't know, we'd have to look at that.

I think the point is that you have to sequence people in the hospital as well, otherwise you won't know if that particular strain is safe or not.

If it is a rare strain, how will you know if it's safe? Seems like it would have to be a rare strain with thousands of cases and hospitalizations in that population are extremely rare.

Sampling bias and other confounding factors would be a real problem in this search, at least from a statistical point of view, imo.

I also think finding everyone who has been infected with a strain isn't feasible, at best you are sampling from the population.