[LeonM]

Same here! I remember I found it such a pain that the embedded toolchains were mostly exclusively for Windows. I dabbled around with cloud9 IDE for a bit, but it wouldn't fit my workflow.

Nowadays the WSL basically made Windows my all-in-one development environment. My stack is WSL, docker and Jetbrains IDEs (but the latter is just a matter of personal taste). I haven't touched my Linux desktop in over a year.

Personally, for my workflow, I no longer see a benefit in running a cloud IDE. But maybe that for junior or aspiring devs a cloud IDE will make it much more easy to get started.

[sz4kerto]

WSL doesn't have access to USB device (well, you can make it work more or less, but it's a pain). So the remote extension is great in this case.

[LeonM]

That is the point that I was trying to make: I used to work on Linux and spinning up a virtual machine to run the Windows tools (USB was also a pain with that).

But now, thanks to WSL I have turned that around. I now run Windows so I can run the windows-only debuggers natively, and still have all the unix tools available through the WSL CLI.

Admittedly I do not do much embedded development anymore, but I'm pretty sure I could launch Windows ICD tools from the WSL CLI.

[evunveot]

Do you run the Linux versions of your Jetbrains IDEs using WSL or the native Windows versions? I was setting exactly this up just this past weekend after 10 years of running Linux exclusively and I'm not sure which way to go.