zlacker

>>tonyst+(OP)
We burned an evening just last week tracing an Intel wifi driver issue to missing kernel headers that required upgrading the kernel to a new, non-LTS version. And only then did we move on to Nvidia drivers.

So no, still not the year of Linux on the desktop. Our entire dev team does it, but largely because Nvidia and Apple stopped working together.

The bigger surprise is Windows WSL2 is just about there for Ubuntu support. We are just blocked on opencl side of Nvidia support (but no ETA.)

>>lmeyer+19
I really tried to make wsl work for the windows users on my team, but we kept getting tangled up with networking (I guess there's a virtual switch involved and so when a tool claims to have forwarded a port it's hard to figure out where it forwarded it to and why only half of your stuff can see it).

Do you know if that situation has improved in the last year or so?

>>__Matr+mj
We got stuck on the Nvidia opencl drivers before we went deep into k8s networking

Our experience with local k8s dev is the issues are more on the k8s distro side. So at least for local dev, I'm guessing the happier path is sticking with KinD approaches wrt WSL2. Our wsl2 docker testing was successful, even w GPUs, and bc of the file system seperation, felt more like native Ubuntu docker's imperceptible overheads vs the painfully slow OS X docker overheads (ex: npm run watch taking minutes vs seconds)