Some might have to die twice then
Boomkop3
https://hamy.xyz/blog/2025-06_7-reasons-fsharp-sucks
The actual article, not whatever this clunky reposting thing is
I might just start bundling my apps inside an environment setup with nix inside docker. A lot of them are similar to identical, So those docker images actually share a lot of layers under the hood.
My apps after compiling and packaging are usually around 50mb. That's 48mb of debian, which is entirely shared between all the images that I build. So the eventual size of my deployed applications isn't nearly as big as they seem from the size of the tarball being sent around. So for 10 apps, that's not 500mb, that's 68mb.
If anything, the docker hub and registry are a bit of a mess.
you can trust the nix repositories aren't going to change
That, I do not. And storing the source and such for every dependency would be bigger than, and result in essentially the same thing as an image.
I think you're trying to achieve something different than what docker is for. Docker is like installing onto an empty computer then shipping the entire machine to the end user. You pretty much guarantee thing will work. (yes this is oversimplified)
The issue is, nix builds are only guaranteed to be reproducible if the dependencies don't change. Which they shouldn't, but you can't trust the internet to be consistent. Things won't be there to be fetched forever.
Images do. And you can turn one into a container in seconds. I suppose it's a matter of preference. I like one a package to be independent
Windows sandbox? Or sandboxie I suppose