True, my terminology was a bit outdated as I keep thinking of pytorch as just the Python wrapper on libtorch. That's not really true. I prefer to avoid Python

True, my terminology was a bit outdated as I keep thinking of pytorch as just the Python wrapper on libtorch. That's not really true. I prefer to avoid Python nowadays due to the pain of dependency management, a nice as this article is don't care to learn about Poetry. So training in pure C++ (or better Nim) is my preferred setup. Keeping a similar build setup for both training and deployment saves a lot of headaches which is why the nimtorch interface is handy even if it's not as full featured/up to date. Now I'm only deploying a very simple NN without much need for experimentation.