vilunov

10 ms·

121.
by vilunov 4y ago
OCI is based on Linux namespaces, which provide a way to create isolated filesystem trees for processes. You probably want that, and I agree with you, but probably forcing this into OCI itself is a lost cause, since its tooling is too based
122.
by vilunov 4y ago
> but that's surely a fault with those tools Honestly I don't think so, in modern Linux namespaces it's perfectly possible to run them in isolated filesystems and to provide whatever they want at whatever paths they want w
123.
by vilunov 4y ago
The main problem is that there are decades of software developed for the classical filesystem, and Nix proposes just to patch that software so that it would be compatible with the "new" way. This is a radical and unneeded change.
124.
by vilunov 4y ago
I personally would prefer a build and environment tool which uses the modern Linux namespaces to prepare isolated filesystems without needing to reinvent a whole bunch of wheels. A number of problems that I would like to be fixed: - Post-bu
125.
by vilunov 4y ago
This isn't what I was talking about, I'm all for being as pure as possible, dial the reproducibility and isolation to the max. Unfortunately, Nix itself as an application is not isolated. It requires a unique installation process
126.
by vilunov 4y ago
This is true, I can put nix apps in a container. It improves the reproducibility of builds, but it still wastes disk space, because the container is still based on layers and not packages. > There is definitely a bit of a learning curve
127.
by vilunov 4y ago
Makes perfect sense to me, sadly. The dependencies are specified in excessively, that's why everyone is shipping Ubuntu. This is caused by and further facilitates the development style of "do not track what we use, just ship every
128.
by vilunov 4y ago
One person's "basic feature" is another person's "a good addition" or even "this might be too much". People use it because they don't feel about it as strongly as you do, and it's been the c
129.
by vilunov 4y ago
That holds only for properties which are describable by the Rust's type system, including mentioned thread- and memory-safeness. Things get worse when it comes to async and futures, since RAII doesn't really work with them, and yo
130.
by vilunov 4y ago
Cargo doesn't update crates automatically.