Comments URL: https://news.ycombinator.com/item?id=48468352

Points: 4

# Comments: 0

But almost all of the shot film was accidentally damaged beyond repair by the Soviet lab — they were using specially imported Kodak film stock that apparently the lab was unfamiliar with — and Tarkovsky had to go back to the Soviet film board and negotiate more money to reshoot the film.

Tarkovsky had been unhappy with the film as he shot it, and during these months of downtime, he repeatedly workshopped the script together with the Strugatskys. Long story short, Arkady Strugatsky proposed that Tarkovsky strip down the story; he wrote a treatment that reduced the entire film to a bare-bones, more philosophical story with nameless characters and very few overt sci-fi elements. Tarkovsky essentially wrote everything around that new core, much of it apparently also written during the second shoot.

I recommend the book "The Films of Andrei Tarkovsky: A Visual Fugue", by Johnson and Petrie, which has a whole chapter on Stalker and the difficulties of making that film.

In my opinion, Roadside Picnic is a masterpiece, and I would have loved to see a faithful adaptation of it. Stalker, as it ended up, is not really an adaptation of it.

Curcumin has been extensively studied, and a common observation is that it is fantastically bioactive in vitro, but tends to have zero meaningful properties when introduced into the biology of a real human being. Researchers have categorized it as an IMPS (invalid metabolic panacea), i.e. a drug whose chemical properties are an illusion, and has ended up becoming a "black hole" for scientific funding [2] [3].

The part about how it "disrupts multiple inflammatory cascades" and so on sounds terrific until you realize these are behaviours observed in vitro. The fact is that curcumin is unstable and highly reactive, so it gets torn apart and neutralized early during digestion, leading to insanely low bioavailability. Tons of compounds are anti-inflammatory in vitro. Very few actually are in the human body.

[1] https://reeserichardson.blog/2024/01/30/the-king-of-curcumin...

[2] https://pubmed.ncbi.nlm.nih.gov/26505758/

[3] https://pubmed.ncbi.nlm.nih.gov/28074653/

Comments URL: https://news.ycombinator.com/item?id=48272673

Points: 1

# Comments: 0

    pub async fn dataset_stats_handler(
        Path(dataset_id): Path,
        Query(verbose): Query,
    ) -> impl IntoResponse {
      ...
    }

    .route("/datasets/{dataset_id}/stats", get(dataset_stats_handler))

Many other things to like: The absence of context.Context, the fact that handlers can just return the response data, etc.

What I don't like: Async.

Comments URL: https://news.ycombinator.com/item?id=48223184

Points: 11

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=48198551

Points: 498

# Comments: 242

Interestingly, in both cases the semantic shift seems to have been caused by the enactment of laws to control drugs. The legal term these days is probably "controlled substance" in English, but "narcotic" now definitely refers to many drugs that are not medically narcotic.

For example, if you map folders like /foo and /foo/bar to numeric IDs, then each file can simply refer their parent folder. Renaming a folder, or moving a folder to a new parent, does not need to update any files.

You can take this a step further and have a three-level split: Tree, file-tree join table, and files. The tree describes the hierarchical structure of folders (which changes more rarely than files do), while the file-tree join table is essentially [folder_id, file_id]. When a file is moved, only the join table (which is much smaller than the files and super sortable and compressible) must be updated.

I take the point that updating multiple discrete pieces of information puts more demand on the transactional layer, which has to ensure atomicity and consistency. But I'm surprised it wasn't even mentioned as an alternative that was evaluated and rejected. The article starts out with the premise that a flat key/value approach is the only choice on the table.

    f: impl FnOnce(Object) -> impl Future
>