List of Windows hiccups with Linux-like development environment

WSL2 distros can freeze when not used. They can’t be terminated, and the whole WSL can’t be shutdown. Reboot is the only thing that helps.
Using an isolated SSH Agent per distro is not straightforward since you can’t really auto-start services.
File-tree synchronization between WSL & PHPStorm can freeze. PHPStorm restart is required.
NPM is substantially slower in WSL2.
A 16GB setup is barely enough. Having a single VM running in the background, and some applications in the user space, gets the system to use ~90% of the available memory.
Starting a new WSL shell can fail with process exited with code 1 for no apparent reason. It works fine on another try.
Exposing a WSL VM to the local network requires extra steps every time WSL’s IP changes.
PHPStan in PHPStorm over WSL + Docker stops working after random intervals.
APO Equalizer gets periodically uninstalled on its own, breaking the audio setup. Reinstallation requires a PC reboot.
Initial WSL2 Ubuntu installation doesn’t have all the dependencies (ex. mesa-utils, libgtk-3-bin) required to run JetBrains in WSl2.
No web-browser integration. Opening URLs in the VM requires the VM to have an actual browser.