[modo_mario]

>It being an complete integrated package from the OS to the IDE is the best feature about dotNet.

In a general purpose development context I consider it a downside. In the same way that I don't consider it a boon for XCode & the like that I can't run it on my machine and will need to go buy a mac.

When it comes to a more general purpose development context I find that a lot of things have this "if you are on windows" asterisk. From recent memory it can go from the rustup installation page just referring to a completely different page or rediscovering that text files having diverging line endings there or needing to do some workarounds when making commandline tools in such low level languages so that they'll also work on windows, needing to bundle some redistributable dll in your installer to make things work on windows even if you used visual studio on windows to make your binary. They'd work everywhere except windows because vcruntime isn't statically linked by default or something. Given PHP being mentioned think this was also the reason it took so long for various PHP functions to become available on windows in the past (Not sure if they're all available now. I haven't kept up). I remember discussions from back then with complaints about Windows being a second class citizen for php when that wasn't really the case rather it was just more often the odd one out.