I can’t remember all the details, but depending on the CPU you are running you may need some extra configuration on opnsense.
There were a few issues, on my servers, running on older Intel Xeon CPUs, but I eventually fixed them adding proper flags to deal with different bugs.
Other than that, running on a VM is really handy.
On nvidia, there are still too many edge cases involving Wayland that are just crippled. Orca slicer doesn’t work for me for example, you are completely missing any of the 3d accelerated graphics in there.
On the other hand, the AMD 7x00 series have different kind of bugs, with ring0 errors leading to full resets.
I think once nvidia drivers are squared out (the proprietary ones) it will be smooth sailing.
I can’t say if you are overstating it but, only mention that I went through a similar path. I had it multiple scripts running and it was a neverending thing.
Since I have moved to small step I never had a problem.
The biggest advantage I got is for products like opnsense, you can do automatic renewal of certificates using your internal CA.
Generating new certs is still as simple (actually much easier for me) than relying on openssl or easyrsa scripts.
You can always compile your own Iosevka and adjust several pieces, I have done that selecting what I consider the best pieces a long time ago.
The compiled font lives in an easy to access internal webserver that I just grab from every computer I use (=
I really love the current trend in R&D PowerPoints
Removed unreadable // Added /* */ on their own lines with fancy design above and below comments
distcc so you can compile on the faster ones and distribute it