Earlier quoted context omitted.
Flox employee here! To start off by addressing how this relates to nix tools: - Our goal is to be more user friendly. You don't have to learn the Nix expression language or understand nix internals to be successful. - We've been able to add some opinionation and polish. Some of that is subjective, but some examples are: - We have a hybrid imperative/declarative interface. You can `flox install && flox list`, and thos…
You know you can just write `nix develop -c zsh` or `nix develop -c fish` or whatever, right?
Show HN: Flox 1.0 – Open-source dev env as code with Nix
71–80 of 201 posts
Re: Show HN: Flox 1.0 – Open-source dev env as code with Nix
#72There are several tools in this space now- nix is maturing and people are realizing how useful nix can be for dev envs. * [devenv](devenv.sh) - I am using it and loving it, but worried that the development is not moving forward * [devbox](https://www.jetpack.io/devbox) * [daytona](https://www.daytona.io/docs/usage/workspaces/) * [devshell](https://github.com/numtide/devshell) * [bob.build](bob.build) more focused on…
It’s a modern version of https://github.com/asdf-vm/asdf written in Rust.
Re: Show HN: Flox 1.0 – Open-source dev env as code with Nix
#73I adore the concepts of nix, but the user experience is awful. Maybe that's what this tool solves? It takes a frustrating amount of effort and incessant config tweaking with little to no documentation and navigating seemingly endless already-deprecated methodologies to reach that point. Perhaps I'm just dumb, or looking in the wrong places.
In any case in my experience the end result is every time I see something related to nix, I find myself thinking "I can't wait til that's easy"
Re: Show HN: Flox 1.0 – Open-source dev env as code with Nix
#74Love to collab on it when you feel the time is right
Ivan cofounder Daytona.io
Re: Show HN: Flox 1.0 – Open-source dev env as code with Nix
#75The line about nix making it easier for newcomers in the readme and similar statements always trigger me. I am quite a competent person and I've never once thought "that was easy" when trying to use nix. I adore the concepts of nix, but the user experience is awful. Maybe that's what this tool solves? It takes a frustrating amount of effort and incessant config tweaking with little to no documentation and navigating…
Re: Show HN: Flox 1.0 – Open-source dev env as code with Nix
#76One critical issue with "power of Nix without the learning curve" kind of products is that you still have Nix behind the scenes, including the /nix/store, which is intentionally not cleaned up by Nix automatically. So when users try out something that hides Nix from them, their drives inevitably fill up, which is super user-friendly because they have no idea how to reduce the amount of storage used. It's different wh…
Just set nix garbage collect to run every thirty minutes.
Re: Show HN: Flox 1.0 – Open-source dev env as code with Nix
#77There are several tools in this space now- nix is maturing and people are realizing how useful nix can be for dev envs. * [devenv](devenv.sh) - I am using it and loving it, but worried that the development is not moving forward * [devbox](https://www.jetpack.io/devbox) * [daytona](https://www.daytona.io/docs/usage/workspaces/) * [devshell](https://github.com/numtide/devshell) * [bob.build](bob.build) more focused on…
Devbox can also run services too. Both products use an awesome process runner called process-compose ( https://github.com/f1bonacc1/process-compose/ ) which is worth checking out (it's even built with nix!)
Essentially taking what you get from the NixOS-specific configuration.nix options (like for example `services.mediawiki.enable = true`) and letting that be per-project, per-directory, is super useful.
Re: Show HN: Flox 1.0 – Open-source dev env as code with Nix
#78The line about nix making it easier for newcomers in the readme and similar statements always trigger me. I am quite a competent person and I've never once thought "that was easy" when trying to use nix. I adore the concepts of nix, but the user experience is awful. Maybe that's what this tool solves? It takes a frustrating amount of effort and incessant config tweaking with little to no documentation and navigating…
Re: Show HN: Flox 1.0 – Open-source dev env as code with Nix
#79https://news.ycombinator.com/item?id=39616709 a few days back daytona was also released. any thoughts on how it differs ?
Daytona solves all the automation and provisioning of the dev environment, actually wrote an article here laying out exactly what we do: https://www.daytona.io/dotfiles/diy-guide-to-transform-any-m...
Daytona currently supports only the dev container (https://containers.dev/) "dev env infrastructure as code" standard, but are looking to support others such as devfile, nix and flox.
Hope this helps
Re: Show HN: Flox 1.0 – Open-source dev env as code with Nix
#80Earlier quoted context omitted.
I once needed to install a specific version of a package on my nix environment. It took me 2 hours to find how... After a few months, I needed to do that again, but now the project supported devenv.sh. It took me 5 min. That experience also repeated for other kinds of tasks, for example: start postgres (or redis or elasticsearch or cassandra...), install packages only if the host system is `darwin`, install old versi…
How does devenv help with using an specific version of a package in an easier way than nix (with flakes)? Does it have any kind of simpler syntax for overlays? Or you are referring to pinning a nixpkgs version? I'm not really against tools that make it easier to use nix, I think devenv is a nice tool and I like that it doesn't hide nix, the same way I love home-manager and use it all the time.
Yep. That's my main argument for it against devbox.
> Does it have any kind of simpler syntax for overlays?
Yes, it does. But what helps isn't that, but the concise docs with just the information I need to know to get up and running quickly: https://devenv.sh/getting-started/
I've read multiple docs/books on Nix, but I always find myself lost when I need to accomplish anything simple. With devenv, I can spot most of my answers from the docs menu. They are all a single click distant from me.