4 ms·
Complexity is relative. I'm a ansible + packages kinda-guy, so of course k8s feels bloated. But Nix with "its compile everything and store the results in deep d
by acatton 4y ago
Complexity is relative. I'm a ansible + packages kinda-guy, so of course k8s feels bloated. But Nix with "its compile everything and store the results in deep directories with sha256 hashe names, and if two programs depends on two different patch versions of sqlite, just compile and keep both in parallel like npm" feels really bloated to me.
- qwerty456127 4y ago> if two programs depends on two different patch versions of sqlite, just compile and keep both in parallel This can make sense in the scientific environment where reproducibility as precise as possible (incl. precise speed and memory usage of every specific algorithm) is very desirable. But in IRL this (different apps ignoring the proper "Unix way" of sharing libraries and updating them independently to the apps, depending on specific versions instead) always is very annoying. Every time I have to run an old app that requires old libs non-existent in my distro version I just symlink the names to the new ones and everything works great. Every time I download a Python project with requirements set to specific versions I replace the requirements with "this or newer", update and everything works great. Theoretically I can imagine a situation when an SQLite version upgrade can break somethiong but practically I can't - I bet this will never happen to me and if it does I'll just pay my bet by fixing the problem manually.