Agree. The issue with reproducibility comes up mostly once you are building your own containers, many of them, and run them in production but then it can hit very hard because it becomes too expensive then to work around all of the following: Once you are hit by a problem (sometimes years after building the original one), it’s hard to debug bc you can’t be certain to be able to reproduce what you have. It’s even difficult to just find out what is in an existing Docker container, companies are running costly scans for that. And finally you can’t compose (you can mostly layer) as well one Docker container with another. Using Nix with flakes gets rid of all of that and you can still have Docker or other containers as output.
“artificial intelligence has the power to save the world”—save it from what exactly?
Could also use Nix as package manager on Ubuntu. It does essentially what you say (symlinking) with guaranteed isolated dependency graphs.
How do sql query engines backed by S3 like Trino (Athena) behave for euch queries?
Thanks, that’s helpful! Is this repeated querying essentially what graph databases do under the hood? Can this be more efficient than multiple joins? Also, what are RDF strategies?
Interesting discussion in the article. Seems like it’s a pretty experimental therapy atm without any conclusive evidence that it works.
But can you really get an autoimmune disease by eating too much supplements? I thought the body would just not retain them. It’d be quite difficult to eat exactly the quantity required without any self regulating mechanisms in place.