4
points
tomberek
Joined 274 karma
[ my public key: https://keybase.io/tomberek; my proof: https://keybase.io/tomberek/sigs/9p1R93wG3L4zZV8AEfIzPqzwtX34Im0PT09B8ykMkJI ]
- tomberekPresumably this would support a big improvement to both SBOM generation as well as various UX features and workflow improvements.
- Trading perfect reproducibility for usability: a pragmatic look at Flox's new features
- 5 points
- This is exactly how I can rapidly prototype things. Once proficient with this tooling is becomes very easy to quickly spin up services and PoCs. Managing it and iterating is also a breeze.
- Random thought. Another commenter worried about the runtime of the program becoming mangled and performing destructive operations on your machine. What if you run the reducer as a source-to-source Nix derivation? Protects against dangerous things, and can be easily distributed to remote builders.
- Agreed. Packaging is different than deployment. Devs should return to the art of packaging, such that their software can be then deployed into containers, VMs, micro VMs, whatever. That is what packaging allows, re-use.
This is the sort of behavior Nix encourages (disclaimer: I work at https://flox.dev , using Nix as our baseline tech). Docker as both a packaging and deployment format can carry a bit of weight, but can quickly get out of hand.
- 5 points
- This is excellent. Have you considered making a presentation or a write-up of the experience?
- 6 points
- 10 points
- A similar article for bringing Ruby into the Nix ecosystem: https://flox.dev/blog/flox-and-ruby
- 8 points
- 12 points
- This is an excellent pattern. Nix uses it to allow one to create a full transitive build graph, serialized that plan, move it around, and execute it in a distributed and reproducible fashion.
There are always temptations to loosen the constraints this imposes, but they nearly always come at a cost of undermining the value of the pattern.
- 4 points
- 2 points
- `flox` needs Nix to function. So the rpm/dev/OSX installers first install Nix, and then installs flox itself.
If you have Nix already, you can try it out as described here: https://flox.dev/docs/install-flox/#install-with-existing-ni....
side-note: with further improvements to Nix as a library, it may be possible to make installing Nix not necessary for flox to function, but this is on a longer time horizon... don't hold your breath
- That link in hub.flox.dev is wrong. The link at https://flox.dev/terms-conditions is correct. Fixing.... thanks!
- The python ecosystem will require specific support, so at the moment we recommend using `flox` to get all of the other things that might not be managed by an existing Python package manager, and/or to install that package manager itself.
Being a general solution, `flox` cannot directly provide the same level of integration as a python-specific tool, but we CAN make it easier to use those other tools, and bring in others.