Reproducibility
Flox provides a consistent and reproducible environment for developing and deploying software, ensuring that applications run the same way on different machines and platforms.
Ease of Use
Flox simplifies the management of dependencies and environments, making it easier for developers to maintain their software setups.
Isolation
Flox offers isolated environments which help in avoiding conflicts between different software packages and their dependencies.
Community Support
As a growing platform, Flox benefits from an active community that contributes to its development and provides support to users.
Promote Flox. You can add any of these badges on your website.
Is the objective to get inside a container to do dev stuff? Reminds me of https://www.jetify.com/devbox and https://flox.dev/. - Source: Hacker News / about 1 month ago
I think it's a bad addition since it pushes people towards a worse solution to a common problem. Using "go tool" forces you to have a bunch of dependencies in your go.mod that can conflict with your software's real dependency requirements, when there's zero reason those matter. You shouldn't have to care if one of your developer tools depends on a different version of a library than you. It makes it so the tools... - Source: Hacker News / 3 months ago
I think that's a bit reductive, but I get the intent. A lot of people see systemic problems in their development and turn to tools to reduce the cognitive load, busywork, or just otherwise automate a solution. For example "we always argue over formatting" -> use an automated formatter. That makes total sense as long as managing/interacting with the tool is less work, not just different work. With Nix I still think... - Source: Hacker News / 4 months ago
Try flox [0]. It's an imperative frontend for Nix that I've been using. I don't know how to use nix-shell/flakes or whatever it is they do now, but flox makes it easy to just install stuff. [0]: https://flox.dev/. - Source: Hacker News / 4 months ago
If you like NixOs and virtual development environments, perhaps try https://www.jetify.com/devbox or https://flox.dev/. - Source: Hacker News / 4 months ago
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,... - Source: Hacker News / 6 months ago
Flox is the best thing I know of for articulating binary dependencies (language runtimes, etc.), which is probably the sweet spot for nix anyways at the moment. Flox uses nix for its backend, but has a simple TOML syntax and is properly humble about what it can do -- but killer at it -- as opposed to promising the world. https://flox.dev. - Source: Hacker News / 11 months ago
Nix and NixOS are in something like the state git was in before GitHub: the fundamental idea is based on more serious computer science than the status quo (SVN, Docker), the plumbing still has some issues but isn’t worse, and the porcelain and docs are just not there for mainstream adoption. I think that might have changed with the release of flox: https://flox.dev, it’s basically seamless (and that’s not... - Source: Hacker News / about 1 year ago
Do you know an article comparing Flox to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Flox. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.