3 ms·

I disagree on the WSL part. As someone who has been trying (in earnest!) to do the macOS -> Windows switch, I have to say WSL has been a letdown. Files you crea

by akulbe 9y ago

I disagree on the WSL part. As someone who has been trying (in earnest!) to do the macOS -> Windows switch, I have to say WSL has been a letdown. Files you create don't get proper permissions. That requires fixing, every time, if your workflow involves moving files from WSL to a deployment target. This is only one of the issues I encountered. At this point, if you're wanting to use WSL for something like Chef development, you're better off having a full Linux VM on your Windows machine, or just sticking with macOS (in spite of it's apparent decline in quality).

nickjj 9y ago
If you're testing a Chef run, you probably don't want to use MacOS because your target deployment OS is likely some Linux variant. You are right about file permissions, it's the one downside I've noticed but luckily it's a non-issue. You can just chmod your files and folders in your deploy scripts/recipes/playbooks. This is a good practice anyways and I would do that in any case. Also in any case, if I were testing deploy scripts I would always do that in a VM or staging server even if I ran Linux natively, because you wouldn't want to corrupt your development box with project specific deploy infrastructure. Oh yeah, the permissions also don't bother you in development. For example I can just cd into my development files (which are outside of WSL) and run VSCode on it without sudo or any tricks, and it all just works. They are accessible from within WSL too without using sudo (even tho they are owned by root:root according to WSL while I'm logged in as my user).