I've never really used a Mac much, but it did cause a problem at a previous employer where most devs on the team worked on Macs natively and then tests would pass locally and fail in CI, because the CI was running on the target Linux config. I'd usually notice them first as I'd run the tests on my Linux VM (pre WSL) and anything with a case mismatch in a config or module import would fail. Was a pain to fix the first time because of bad assumptions about the Mac env, but subsequent issues were quickly fixed.
One big issue I ran into with WSL (not sure it's been fixed, not an issue for me anymore) was building large C++ projects under WSL with MacAfee installed. Apparently a known issue, but it (MacAfee) would leak memory like a seive as it scanned the files in a way that wasnt recoverable. The only way to get the memory back was to reboot. Even after the processes in WSL ended, the memory was lost. You couldn't see what process was using the mem. But, it showed in the system utilization. It is possible to hard freeze Windows due to this bug. Solution? Uninstall MacAfee. Had to have an antivirus due to company rules and (I think) financial regs, but Defender didn't leak memory and was sufficient (albeit slow while building). Don't know if it's still an issue as I haven't used that configuration in close to a year and a half.
There have been issues with the Console Host (I noticed artifacts using Vim in bash under WSL under certain circumstances), good news is that the Console Host is getting much needed love and is probably getting the most attention it has in over a decade. Its already improved quite a bit, and some big changes are coming soon. Also, the team behind it is very engaged on Github issues (the source isn't available, but they use GH for issue tracking directly from the public without having to use the Feedback Hub or file an issue with MS support).
