Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Flox Open Beta

floxdev.com

Post reply on HN
Print view View original

11–20 of 59 posts

Re: The Flox Open Beta

#12

Post by tomberek »

sleey wrote: post #11

This looks similar to https://www.jetpack.io/devbox/ that build on top of nix too.

We see a few tools that do a similar built-on-top-of-Nix approach, so we released a Rust library that makes using the "command line API" in a more type-safe manner: https://github.com/flox/runix

Re: The Flox Open Beta

#13

Post by ronef »

sleey wrote: post #11

This looks similar to https://www.jetpack.io/devbox/ that build on top of nix too.

It's exciting to see so much starting to be built with and on top of Nix. We've been working on enabling developers to go beyond the developer environment and into the later stages of the flow. Curious to get your thoughts on what you find the most compelling from the core Nix story/benefits.

Disclosure -> Ron here, co-founder at flox and NixOS Board Member

Re: The Flox Open Beta

#15

Post by sleey »

ronef wrote: post #13
sleey wrote: post #11

This looks similar to https://www.jetpack.io/devbox/ that build on top of nix too.

It's exciting to see so much starting to be built with and on top of Nix. We've been working on enabling developers to go beyond the developer environment and into the later stages of the flow. Curious to get your thoughts on what you find the most compelling from the core Nix story/benefits. Disclosure -> Ron here, co-founder at flox and NixOS Board Member

For me, it's reproducibility and version control.

I started from using asdf [1] for managing golang, python and node. My main language is golang but often I need to run project from other language and different version especially python with packages have different version needed from pip i.e python 3.6 and python 3.8

I found about nix and it looks a good fit for my usecase because it not messing with PATH and not spawning container like docker but when I try to use it, I feel overwhelmed by it.

I use devbox now because it's easy to use but definitely will try flox. I welcome any tools that can help reduce nix complexity.

[1] https://asdf-vm.com

Re: The Flox Open Beta

#16

Post by tomberek »

sleey wrote: post #15
ronef wrote: post #13

Earlier quoted context omitted.

It's exciting to see so much starting to be built with and on top of Nix. We've been working on enabling developers to go beyond the developer environment and into the later stages of the flow. Curious to get your thoughts on what you find the most compelling from the core Nix story/benefits. Disclosure -> Ron here, co-founder at flox and NixOS Board Member

For me, it's reproducibility and version control. I started from using asdf [1] for managing golang, python and node. My main language is golang but often I need to run project from other language and different version especially python with packages have different version needed from pip i.e python 3.6 and python 3.8 I found about nix and it looks a good fit for my usecase because it not messing with PATH and not sp…

We think the ability to hopscotch between projects and ecosystems without fear is a key value proposition of Nix-based technologies. Our approach is to address the entire user experience from installation and docs all the way to developing, building, publishing, orchestrating, and sharing your software. It is not all ready - we can't do all of it at once; we are laying down the framework.

Please give us a try and offer any feedback, we want to make it easy to adopt for even non-Nixers and enterprise.

Re: The Flox Open Beta

#17

Post by ptannor »

I know that this has been asked in past threads but I would love to understand how Nix compares to containers and on top of that what does flox provide in it's comparison to containers?

Re: The Flox Open Beta

#18

Post by pikanix »

sleey wrote: post #15
ronef wrote: post #13

Earlier quoted context omitted.

It's exciting to see so much starting to be built with and on top of Nix. We've been working on enabling developers to go beyond the developer environment and into the later stages of the flow. Curious to get your thoughts on what you find the most compelling from the core Nix story/benefits. Disclosure -> Ron here, co-founder at flox and NixOS Board Member

For me, it's reproducibility and version control. I started from using asdf [1] for managing golang, python and node. My main language is golang but often I need to run project from other language and different version especially python with packages have different version needed from pip i.e python 3.6 and python 3.8 I found about nix and it looks a good fit for my usecase because it not messing with PATH and not sp…

we wrote a post which may illustrate flox vs asdf https://floxdev.com/blog/asdf-migration
Post reply on HN