If the author like NixOS, they can use NixOS in native, and then they can get native Ollama again. No need to run nix on WSL

The clue seems to be "on your gaming PC". Many linux users still run Windows on their gaming machines due to compatibility. This would also probable be their device which has the most powerful GPU.

They can not game on it (yet). That was the point of this post. Having a 2 in 1 device. For gaming and on demand ai.

Too heavy, too complex and too slow.

Although ansible can be used in local machine, but it is design for multiple remote machine. For example, if you want copy a config file to target, you must use some tools like `scp` or do some hacking. And it's much slow than shell script, and the print in stdio is ugly. (because it's design for running in 100 machines in one time.)

Ansible also had a steep learning curve, and redhat did not prepare a good beginner's manual for it. Searching the web there is only the experience of people who have used it for years, each with their own way of writing. There are no best practices for getting started easily.

> if you want copy a config file to target, you must use some tools like `scp` or do some hacking

Maybe I misunderstood, but I use copy (1) for this in Ansible. This is standard, and you shouldn’t need scp?

(1) https://docs.ansible.com/ansible/latest/collections/ansible/...

Ansible has a steep learning curve? The easiest thing to do is just a list of steps (playbook) and I'm sure that is in the getting started docs.

Modularizing complicates things obviously but for simple uses I don't see how it can be simplified much further.

Yes, it was harder to master than terraform and even k8s. Their documentation was the reason, in most cases.