quadhome

Couldn’t a company incinerate funds and their stock bottom out because no one will buy?

Was your response facetious? The AI labs literally do this, right now.

— via https://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Disp...

The DA is serious about "in any matter."

Get me press just like the frontier labs by admitting to crime. Make no mistakes.

In the words of Derek Lowe:

Amyloid-directed therapies truly, truly do not appear to be the answer for Alzheimer’s treatment. When I started work in the field back in the early 1990s, I was convinced of the opposite - the evidence looked very strong that defects in amyloid processing were indeed the cause of the disease. But that was thirty-five years ago, thirty-five years in which therapy after therapy after therapy aimed at amyloid mechanisms has failed.

[…] We’re way past persistence, way past focus, way past optimism and multiple shots on goal and old-college-tries. Do something else! For God's sake, do something else.

— https://www.science.org/content/blog-post/anti-amyloid-antib...

Also, it’s a loooong way from the self-contained goal—- there are a lot of third-party crates as dependencies still.

Yikes.

This idea may be desirable; but, a deadlock is possible if there's a dependency between the two operations. The crux is the "and then continue," which I'm taking to mean that the first operation is meant to pause whilst the second operation occurs. The use of `&mut` in the code specifically enables that too.

If it's OK for the first operation to run concurrently with the other thing, then wrt. Tokio's APIs, have you seen LocalSet[1]? Specifically:

    let local = LocalSet::new();
    local.spawn_local(async move {
        sleep(Duration::from_millis(500)).await;
        do_async_thing("op2", lock.clone()).await;
    });
    local.run_until(&mut future1).await;

[1] https://docs.rs/tokio/latest/tokio/task/struct.LocalSet.html

Insane take. Just GPS, MRIs (high temp. supercondutors), electron microscopes, quantum computing, and chip fabs alone are relevant to us here at HN.

Use .run.

  return LoggerStorage.run(requestLogger(), () => {
      logger()?.debug({ url: request.url }, "Started processing request!");
      return NextResponse.next();
  });

I recommend Judith Flanders' "A Place for Everything" as a both a history and survey of the constraints in sorting and organising information in an alphabetic language. It's also a fun read!

tl;dr why would we want an LLM do something as inefficiently as a human?

[1] https://en.wikipedia.org/wiki/WebSub

Beware: low ratings on Rotten Tomatoes, "frustrating close to being great."