3 ms·
In my case, it's the most sane option for Rails development on a Windows environment. My workplace have no love for macOS or Linux distros so I'm bound to Windo
by pelagicAustral 3y ago
In my case, it's the most sane option for Rails development on a Windows environment. My workplace have no love for macOS or Linux distros so I'm bound to Windows 11, I do also work with a lot of Desktop implementations in C# so it half-way makes sense.
WSL slow things down quite a bit, starting/stopping a server, deployments, git workflow... Even then still beats having to run things on a VM an it is better that the hell it was to set up dev environments in Windows before (for anything not .NET)
- baq 3y ago> WSL slow things down quite a bit, starting/stopping a server, deployments, git workflow... There's zero reason (and has been for quite some time, at least a couple years) for those things to be slow - the trick is to 1) make triple sure you're running WSL2 and 2) never store anything on the Windows drive, keep everything in WSL2 home directory. it's basically native Linux speed then.
- Mrdarknezz 3y agoI made the mistake to store it on the windows drive. When I moved it I was blown out of the water of the performance. I got some insane speeds that I didn't think was possible
- baq 3y agoExactly - and you can still access it from Windows with \\wsl$\ if you need it.
- Mrdarknezz 3y agoYeah but if you're a n00b like me and prefer using a git client I had to install it in wsl to be able to use it for some reason
- pelagicAustral 3y agoAh! thanks for the tips! I just set up a new environment and will be testing speeds for sure, yeah, I was using the /mnt/ path structure to reach the projects from the Windows file system.