You probably already know but beware of cross platform file operations with WSL2. That’s the one area it really sucks at. Which is lame because that was like the whole point of WSL1.

Reply to this note

Please Login to reply.

Discussion

“Oh, your file has a space in the name? Go fuck yourself”

Well aware lol

Yes, they recommend against accessing windows files from WSL. Very simple to copy paste though.

Not suitable for a project with huge data though. I’ll admit that.

Have they solved the memory issue with wsl2?

I didn’t have any problems there that I remember. Link me?

Same. I was literally like, “What memory issue?”

My guess is this is fixed. I use it daily with vscode and clion, often for very large builds, and have not noticed anything like this.

Yea I’d bitch about that if I saw it.

Agreed. I also game on this machine, so it’d press my buttons. 🤣

Wsl was my gateway to Linux 😂 when I was running into this problem I just decided to go full force because the development workflow was just so conducive for me

I felt the same way.

Then my boss bought me a computer with an Nvidia video card, and asked me to develop OpenGL code.

For me that was the year before grad school. They dont care what you work with, so long that you work 🤣. Been fortunate enough in that aspect and all the lovely quirks that come with it