I didn't see it in the comments, but FWIW you can choose specific dependencies. You can use regular [dependency specifiers](https://packaging.python.org/en/latest/specifications/depend...), see [PEP 723](https://packaging.python.org/en/latest/specifications/inline...).

Re: b. This is a place where remote standard dev environments are a boon. I'm not going to give each dev a terabyte of RAM, but a terabyte to share with a reservation mechanism understanding that contention for the full resource is low? Yes, please.

I wonder if anybody has used PostgREST (https://docs.postgrest.org/en/v12/) and explored this could provide a comparison. They seem largely similar with PostgREST having some feature advantages associated with being built on Postgres. Where does Manifest have an advantage?

The most obvious point of comparison is that this project doesn't actually use a real database engine, so you're basically guaranteed poor performance with large data sets and have no way to do fine-tuned indexing/joins/filtering.

We need a to-do app following these principles... then another for product management.

R is the better EDA language by far. Python has caught up a lot. Notebook diffs are now readable in git with the right tooling, that's huge.

The drum about not fitting into data pipelines... if you're literally using a bash pipe its true most R programmers have no idea how to do that. Otherwise, that is where Docker and k8s shine.

On packaging. R's package authority runs tests and ensures that all packages work with the latest version of their peers. The dependency heck is much less deep as a result.

We use R at my employer still because we put statistical data science into production. Our experts come to us comfortable with R. Reimplementation would be absurd.

Out of context (and with limited knowledge) comment 3 seems terrifying.

I assume you mean this part:

> We will clobber any previously installed version of this package, even if it breaks whatever else is installed. It's the user's job to make sure that is all sorted out ahead of time.

But this is a `make install` recipe, and I think this is generally expected behavior when running that command. Typically, this would be run in a chroot when building a package.

Relax, don't do it. When you want this, you're turning the relations in postgres into a contract. No service gets to persist internal state. If you're _really_ committed to domain driven design it could work... but you'd be better off with a light (but real) event driven system.

The relations in the database _are_ a contract whether you like it or not.

Event-driven anything is 1000x more complex.

Effect size g is in units relative to variation. It's a corrected version of Cohen's d for cases of unequal variance between groups.

Right on the linked page is commentary about how the title is misleading. https://www.nature.com/articles/s41598-020-62398-w

The HN title should really reflect this. It's a disputed paper.

I expect the emails themselves are just formatted strings. You could use an email parser to get the structure back out. You or someone else mentioned Zapier webhooks, so https://parser.zapier.com/ might be extra relevant.

Ah, haven't heard of parser.zapier.com before. Yes I mentioned Zapier! This could be perfect, will report back.

If Zapier Parser doesn't do the job for some reason, hit us up @ https://parseur.com (co-founder here)