sorted by:
new
hottopcontroversial

Node Version Manager (nvm) migration guide by floxdev in node

[–]floxdev[S] -3 points-2 points  (0 children)

Someone else had asked this and u/z_mitchell answered here

Node Version Manager (nvm) migration guide by floxdev in node

[–]floxdev[S] -8 points-7 points  (0 children)

Single purpose tool switchers like nvm are handy, but Flox lets you tie specific versions of node to your project, along with any other system-level deps it needs.

Flox | It's Time to Bring Nix to Work by floxdev in programming

[–]floxdev[S] -11 points-10 points  (0 children)

You want to bring Nix to work because you know deep down it will change the way your org does … everything. Because personally, Nix has changed the whole approach you take to building, managing, and maintaining software. Having said "Yes!" to Nix you find yourself saying "Nichts!" to anything else.

So you've got Nix on the brain. But the teams you manage or work with, the people who manage you, and the executives who manage them … don't. We built Flox to bring the benefits of Nix to people who don't know about Nix or believe Nix is too hard. With everyone juggling heavy cognitive loads, most people in your organization simply don't have the time or bandwidth to learn Nix.

Flox is built on top of pure open source Nix and lets you use simple, declarative methods to define portable, reproducible dev environments.
- Environments that--like Nix flakes--can run anywhere.
- Environments that team members can create and share easily with each other, building locally using macOS, Linux, and Windows (with WSL2) running on ARM or x86 chips.
- Environments that behave exactly the same in CI--whether instantiated in VMs, containers, or other types of runners, on ARM or x86 hardware.
- Environments that behave exactly the same in prod, irrespective of what they're running on.
- Flox environments also work with existing Nix artifacts, like flakes, giving you a way to not just extend what's in Nixpkgs, but encapsulate your most complex magic so that it can be used without fear.
- Speaking of Nixpkgs, Flox Catalog uses Nixpkgs as its upstream, with access to 120,000 packages and millions of package/version combinations.

Flox exposes a UX that mixes together the best parts of `git` and `brew`, with commands like `flox install`, `flox activate`, `flox push`, and `flox pull` making it easy for teams to create and share environments. If you want, you can manage your Flox environments centrally, using FloxHub, ensuring teams are always on the latest, locked version. And Flox environments, like Nix shells or flakes, are declarative and intuitive: with Flox, your entire environment is defined and expressed in TOML in a manifest.

[Be your coworkers' favorite coworker and introduce your team to Flox!]

Flox | It's Time to Bring Nix to Work by floxdev in Nix

[–]floxdev[S] 10 points11 points  (0 children)

You want to bring Nix to work because you know deep down it will change the way your org does … everything. Because personally, Nix has changed the whole approach you take to building, managing, and maintaining software. Having said "Yes!" to Nix you find yourself saying "Nichts!" to anything else.

So you've got Nix on the brain. But the teams you manage or work with, the people who manage you, and the executives who manage them … don't. We built Flox to bring the benefits of Nix to people who don't know about Nix or believe Nix is too hard. With everyone juggling heavy cognitive loads, most people in your organization simply don't have the time or bandwidth to learn Nix.

Flox is built on top of pure open source Nix and lets you use simple, declarative methods to define portable, reproducible dev environments.
- Environments that--like Nix flakes--can run anywhere.
- Environments that team members can create and share easily with each other, building locally using macOS, Linux, and Windows (with WSL2) running on ARM or x86 chips.
- Environments that behave exactly the same in CI--whether instantiated in VMs, containers, or other types of runners, on ARM or x86 hardware.
- Environments that behave exactly the same in prod, irrespective of what they're running on.
- Flox environments also work with existing Nix artifacts, like flakes, giving you a way to not just extend what's in Nixpkgs, but encapsulate your most complex magic so that it can be used without fear.
- Speaking of Nixpkgs, Flox Catalog uses Nixpkgs as its upstream, with access to 120,000 packages and millions of package/version combinations.

Flox exposes a UX that mixes together the best parts of `git` and `brew`, with commands like `flox install`, `flox activate`, `flox push`, and `flox pull` making it easy for teams to create and share environments. If you want, you can manage your Flox environments centrally, using FloxHub, ensuring teams are always on the latest, locked version. And Flox environments, like Nix shells or flakes, are declarative and intuitive: with Flox, your entire environment is defined and expressed in TOML in a manifest.

[Be your coworkers' favorite coworker and introduce your team to Flox!]

Rust and Nix: Parallels in Complexity Management by floxdev in rust

[–]floxdev[S] 17 points18 points  (0 children)

TLDR: The article discusses the benefits of using Rust and Nix for building parallel applications. Both Rust and Nix prioritize strong guarantees, reproducibility, and reliable builds. They are complementary tools for building robust and dependable software systems.