SuperSandro2000

I always forget to explain that. Atomic updates are one of the best if not the best feature of nixos.

> Is there a nix config wrapper for systemd-networkd?

The options under systemd.network almost map 1:1 to systemd-networkd ones.

So far no one mentioned that you can: - easily cross compile packages: pkgsCross.aarch64-multiplatform.hello - NixOS has modules to get complete services like Nextcloud, Mastodon or Matrix Synapse up and running within minutes including nginx configs - it is possible to switch Desktops and clean up all packages

Yes, that's correct and then you need to tell it which driver you need for your hardware. For example like:

hardware.opengl = { extraPackages = with pkgs; [ intel-compute-runtime # OpenCL library intel-media-driver # video encoding/decoding hardware accerlation ]; extraPackages32 = with pkgs.pkgsi686Linux; [ intel-media-driver # video encoding/decoding hardware accerlation ]; };

Most of the time you can just use autoPatchElfHook and add the missing libraries to buildInputs. I can't remember when I last looked at patchelf itself.

I must admit I got a long way with contributing without knowing much about functional programming. Most things done in mkDerivation especially the basic ones almost abstract the functional and lazy part away.

1. Yes, you need to know some more things but in particular not linking. I have no idea about linking or what to do when it fails with weird symbol errors. If you have a standard autotools, cmake or meson setup it might be as easy as just adding the packages to nativeBuildInputs and it works. The more custom stuff the project does the more you need to hold it hands.

3. For example here https://nixos.org/manual/nixpkgs/unstable/#chap-hooks

5. It is quite the opposite. If the typical build instructions are ./configure; make; make install then you might only need to specify the install directory to $out and you are done. Looking at ldd is also not usually required when compiling from source.

I would highly recommend to use systemd-networkd based networking which should be able to do almost everything if configured correct.

That page is missing the opengl drivers which you also most likely want in the 32 bit variant.

Creating a basic nix derivation is easy and if you don't want to upstream it you can take all kinds of dirty and impure shortcuts.

You almost never want to invoke patchelf by itself but use some wrapper like autoPatchelfHook, FHS, nix-ld, nix-autobahn, etc.

Since 2018 a lot quite a lot happened. Give it another chance.

I want to use the expensive hardware I own and from the few examples I have seen guix is incredible verbose often requiring two to three times the code to express the same thing as nixpkgs.

The lines are often blurry because they are quite interlacing and all where purpose build for each other.

> python310.withPackages and python311.withPackages

I think that should be solvable by supplying them the same function.

env = ps: with ps; [ numpy toolz ] python39.withPackages(env) python310.withPackages(env)

A FHS adds slight overhead to a package and to launch times. It also shadows part of the file system. For example /lib would probably be different for every other program which would be even more confusing.

As soon as you have multiple machines with shared configs it gets really attractive again.

or https://github.com/Mic92/nix-ld or a FHS. There are many projects to help with this.

Yes, you cannot just download any random binary from the internet unless you use a FHS because those libraries are compiled for Distros using a default file system layout.

NixOS is a reproducible, customizable, programmable and adaptable Linux distribution.

Docker is not repeatable. If I try to build the same Dockerfile in 12 months then I likely do not get the same output and it wouldn't be surprising if it does not build at all.

> some people refer to it as "nixlang"

more commonly just nix language or you know it out of context

> naming conventions for Nix are absolute shit across the board

No, not really. They are not consistent for every part and not every package is up to date with everything but if you get the gist you can easily guess things. If things are really weird we can always rename them.

you can also use https://github.com/Mic92/nix-ld or build a fhs.

but in contrast to ansible it uses a real programming language and not turing complete yaml

NixOS has a steep learning curve but if you start to climb it, it is probably the strongest distro right now especially if you want to customize things and have it reproducible.

nixpkgs is already one of the largest package collections. There is a good chance your software is already included.

The nix language itself is pretty straightforward and if you know haskell your should feel straight at home.

You shouldn't use nixpkgs python packages as a replacement for your python development. That would also not work that great on other distros.

steam-run is just a fat wrapper around bubblewrap fhs. If you want to optimize your system you can easily build a smaller one yourself.

Have rich parents. Add ready as that.

and despite all this crap, Germany somehow is still relevant in the world. Baffling.

It's only for a GmbH and the minimum liability. You can also found a UG but then your private money is on risk.

but why?!

I get shiny new stuff syndrome vibes everytime there is a new editor that claims to be perfect and magically solve all problems.