I totally feel your pain. I was in the similar situation, but back then the wsl1 was quite bad. I used vim in normal windows cmd but for some reason it was much slower than on Linux (especially bigger files, not to mention if I added some plugins).
In WSL it was better but I had to run it without Xserver as it was just too slow in the corporate environment. My suspicion was that the firewall we had was slowing it by checking every request to the server
I also learned that windows is not settings the TERM variable. It was a problem for some terminal apps while others kept crashing when it was actuall set. So I had to set it and unset it when I ran some utilities (ssh, lf etc).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I totally feel your pain. I was in the similar situation, but back then the wsl1 was quite bad. I used vim in normal windows cmd but for some reason it was much slower than on Linux (especially bigger files, not to mention if I added some plugins).
In WSL it was better but I had to run it without Xserver as it was just too slow in the corporate environment. My suspicion was that the firewall we had was slowing it by checking every request to the server
I also learned that windows is not settings the TERM variable. It was a problem for some terminal apps while others kept crashing when it was actuall set. So I had to set it and unset it when I ran some utilities (ssh, lf etc).