Linux

While all of it is doable, be aware that it takes time and effort to learn Nix and NixOS. It can be difficult to figure out how to get a particular environment set up properly. There is a lot of documentation, but it doesn't always give easy answers if you have specific requirements for a particular dev environment and such.

It's been a few years since I worked with Unity3D professionally, but I did so in NixOS with very little trouble. Rust has very good Nix infrastructure and so do many other languages. I can't tell you anything about UE5 or the other proprietary tools, but there are FHS-compatibility helpers (steam-run usually works fine when I need to run arbitrary binaries made for 'normal' distros).

If you're willing to figure things out sometimes (and especially in the beginning) and are motivated to take your OS to the next level, NixOS is definitely worth it. Been using it for many years and I can't imagine ever using a mutable OS again as a daily driver (unless the way I use my computer drastically changes). I configured everything just the way I want it; it's magical to have almost everything in one place and being able to try different things without fear of breaking something.

https://nixlang.wiki/en/tricks/distrobox

https://distrobox.it/

Not the nix way, but when you really need something to work, you can create containers of other distros.

NixOS is a Linux distro that does a lot of things differently (for the greater good), and gaming is heavily Windows thing, which is hard to do even on conventional Linux distros (its getting better tho). That said as for your points:

1a. One of the things that would help you, is programs.nix-ld.enable = true; (for more info check https://github.com/Mic92/nix-ld , but its integrated in NixOS already)

1b. UE5 pull request has some things that might help (eg: you could just try running it with steam-run): https://github.com/NixOS/nixpkgs/issues/124963

2. Depends how you are building them, I am not a gaming developer nor tried to build a game without packaging it with Nix. But if you manage to run the UE5 I guess the procedure would be the same as long as you have all of the dependencies available for UE5

3. I am using qemu/KVM on NixOS to run games on with quite a good performance, so that should not be a problem

Yeah, university is almost certainly going to expect you to be able to install Unreal or Unity, which just isn't possible AFAIK on NixOS. NixOS is very all or nothing. You can't just remove the restrictions for one project and hack something together to hit an assignment deadline. Theres still lots of pain points with LD_PATH and 3rd party binaries.

That said, you can use nixpkgs on non-nixos and still get reliability for Godot and other open source tools. For your case, I highly recommend dual booting, and then using nixpkgs without going full blown nixOS.

I went from Arch to NixOS and I've been loving it. I also had all the time on the world to dive in with several machines to fall back to.

There are a lot of layers to wade through especially when you need a specific tool like your UE5 case. As others are saying, there are ways to make everything work, nix or non-nix, it's just more to work through after getting the bases covered.

Anecdotally, I had little trouble getting set up on my MSI laptop with an RTX2070, Primus and all. That was after learning the ropes on a Ryzen IdeaPad.

Rambling aside, I would definitely make sure to start in a non-mission-critical way, but do jump right in if you're comfortable. Maybe if you can stomach the Asus a bit longer, or get the Framework set up and play around with the Asus. And ask plenty of questions! I know I'm not alone in jumping in on nix questions any way I can :)

Skip nixos, it's just going to be a lot of pain for almost no gain. Instead use nix with home-manager on a different distro.

I went from Arch to MX (Debian) + Nix. It's a perfect combo because I get stable system packages, unstable user packages, and I don't have to deal with all of the nixos downsides.

This could be a case for a more stable distro as base and distrobox for your development environment (in Arch, Bazzite, or Tumbleweed).

Following with interest (as I am a newbie myself), but if I were in your shoes, I wouldn't want to re-invent the wheel in the middle of classes. That said, I am loving the process of jumping in feet first on laptop hardware, but the slog is real.

In other news, Arch continues to be rock-solid, even during the Plasma 6 update cycle I've had nothing but success where it is concerned. Best of luck!

For my use the best solution i found so far is setting up the os stuff and tools i use a lot with nix and nixos and then using a debian distrobox for things that i just want to work. Nixos is really good for development but only if the thing youre developing already has a nix development environment or youre the one creating it. For most random github projects you wanna work on/compile etc using something traditional is better. I dont care if one of my distroboxes break i know nixos will always work and boot or i can roll back.

Slightly off-topic here, but have you considered Fedora? For me it just gets the job done and stays out of my way. I don't want to configure a whole bunch of things before I can get to work so I find fedora simple to use and well-integrated. Docs and forums are quite helpful too.

1. NixOS can run binaries well using nix-ld or nix-alien, those will work for the large majority of software. If you run into any trouble, you could always use distrobox as well. Some of this software will also likely be packaged in nixpkgs or other repos.
2. You should be able to build binaries the same way you can on other distros
3. GPU pass through works the same on NixOS as other distros, but parts of it will need to be configured in your systems configuration, which may be a bit complex, especially if you're new to the Nix language. Here's a good article on setting it up.

1. Jetbrains toolbox is proprietary and I can still run it. You do have to explicitly state that you want proprietary software. You can even run random binaries if you setup nix-ld.
2. The preferred way to do this is by creating a shell.nix for each of your projects with the dependencies defined within.
3. Not sure about passthroughs, but qemu worked fine for me.

As for nix Vs arch, I still prefer arch. This is not because nix is bad, but because I have used arch for a long time. I use nix on my laptop because I want that reliability, but I will probably never switch to nix on my desktop. I still find that I can debug my mistakes easier on arch, but with nix I can just git checkout oldcommit. With that being said, I do have a distrobox container with arch in my nix machine, if I really wanna install something quickly.

Do you have a manual arch setup or did you use an install that configured it?

Why Nix? It will only make your life 2000% harder and quite frankly makes one hate Linux. As a developer the best dev distros I've used were Debian, Ubuntu and Arch