@lemmon Based on your two questions, it sounds like you're trying to weigh pros and cons of VCS/PHPStorm and wondering about developing on Windows WSL2.
I have nothing to contribute to the Windows/WSL2 part, but I can say I highly prefer VSC to PHPStorm. PHPStorm honestly feels bloated (totally imo) and my workflow in VSC is super clean/it does everything I care about.
If you try out VSC, I recommend using the Laravel Extension Pack, PHP Namespace Resolver (to import/click through to classes), PHP CS Fixer (to auto-format code to PSR spec).
@lemmon I do use VS Code. I have used PHP Storm but honestly felt like VS Code was more intuitive / free and frankly faster for my workflow. I also liked the level of control I have with customization. I'm sure PHP Storm has a lot of this ability but the learning curve seemed more straight forward so I stuck with VSC. I've been using it professionally as my daily driver code editor (pseudo-IDE) and haven't looked back.
Besides, Phpstorm is still using "Expose daemon on tcp://localhost:2375 without TLS".
Docker saying: Exposing daemon on TCP without TLS helps legacy clients connect to the daemon. It also makes yourself vulnerable to remote code execution attacks. Use with caution.
in addition - it took me a while to find out. So .. VSC
