[poolopolopolo]

except you cant deploy Nix files, and even if you could, better be sure that every employee is using Nix and have the same configuration. The whole point of docker is to make reproducible builds everywhere, not just your computer.

[pmarreck]

> except you cant deploy Nix files

NixOps and nix-deploy: EXIST! https://arista.my.site.com/AristaCommunity/s/article/Deploy-...

> better be sure that every employee is using Nix and have the same configuration. The whole point of docker is to make reproducible builds everywhere, not just your computer.

lol, "tell me you never used Nix without telling me you never used Nix" because it literally guarantees that, each project is a pure environment with no outside influences. THAT IS LITERALLY ITS ENTIRE PURPOSE OF EXISTENCE lolol

I absolutely guarantee you that you will have more reproducible builds with Nix than with Docker. I know, because I've worked with both of them for months on end, and I've noticed that it pains me to work with Docker more than it pains me to work with Nix (hey, it's not perfect either, but perfect is the enemy of good in this case)

[poolopolopolo]

First you are tightly coupling your CI to your developers machine, that in itself is already a pretty bad idea. Second, if one employee wants to install htop on their machine, then every employee will have to install it, this can quickly become a problem when you have 500+ developers. Third, I think you missed the first part on the second quote, you are FORCING every developer to not only use linux but also to use one distribution that is pretty niche.

[pmarreck]

> First you are tightly coupling your CI to your developers machine

It's not like you can't configure builds differently based on an ENV variable, which is exactly what most build tools already do.

> Second, if one employee wants to install htop on their machine, then every employee will have to install it

There's actually a way to install things on the fly on first use. That way, if you never use it, it will never install. If you use it more than once, it will use the locally-cached version. Next?

> this can quickly become a problem when you have 500+ developers.

Nope. Already answered. Plus, you can allow some things into the "pure" environment if you wish. Harmless things like btop or htop, for example.

> Third, I think you missed the first part on the second quote, you are FORCING every developer

What part of "everyone has to use slow-ass non-deterministically-building Docker" is NOT "FORCING" every developer to use something? LOLOL. Plus, on Macs (which USED to be my preferred dev machine) it's slow as fuck, which is why I had to switch to a linux laptop anyway, which is why I said "fuck this" and installed NixOS and went to town instead.

> to not only use linux but also to use one distribution that is pretty niche.

First of all, wow, you are naïve. No good thing DID NOT start out "niche". Literally every technology I've gotten into except for ASP.CRAP was "niche" when I got into it- from Ruby, to Postgres, to Elixir, to Jquery (at the time)... Do not judge things based on their popularity because that's the Appeal to Popularity fallacy. Judge things based on their promise, young padawan. And Nix... promises much.

[pxc]

Docker already requires everyone to use Linux, which is why Docker Desktop is just a frontend for a dog slow VM on your Mac or Windows box.

[ParetoOptimal]

> First you are tightly coupling your CI to your developers machine, that in itself is already a pretty bad idea.

How?!

[pxc]

On systems that have the same containerization feature that Docker requires, i.e., Linux systems with recent kernels, you can use nix-bundle¹ or the flakes-based experimental command inspired by it, `nix bundle`² to generate an all-in-one binary that you can run without installing Nix on the target.

1: https://github.com/matthewbauer/nix-bundle

2: https://github.com/NixOS/bundlers

[ParetoOptimal]

> except you cant deploy Nix files

Ooh let me try...

"except you can't deploy Dockerfiles"

With docker you deploy the artifact, same with Nix. Nix can also create docker images.

> , and even if you could, better be sure that every employee is using Nix and have the same configuration.

How is this different than employees needing to have the same docker version?

In a large org, either will likely be provisioned.

> The whole point of docker is to make reproducible builds everywhere, not just your computer.

No.

Docker doesn't make reproducible builds, it makes repeatable builds.

The whole point of Nix is to make reproducible builds everywhere.