While I don't think my C++ or C# is an example of modern and idiomatic Windows programming, I wouldn't say I know "nothing of Microsoft technologies that have been used for the last half decade and more". I sure haven't used them, but that doesn't mean I haven't read about them.
You mentioned you used "Assembly, Turbo-C, Turbo-Pascal, Borland C++, Java, Javascript, Perl and many, many others", and, apart from JavaScript, none of them is closely associated with modern non-Microsoft development. I initially questioned you about it because, like myself, lack of knowledge of other options may hinder your ability to clearly assess a given technology's advantages.
>You mentioned you used "Assembly, Turbo-C, Turbo-Pascal, Borland C++, Java, Javascript, Perl and many, many others", and, apart from JavaScript, none of them is closely associated with modern non-Microsoft development.
Yes, but the difference is I'm not criticizing modern non-Microsoft development.
Sure. But when we say X is great it is somewhat implied it's great compared to non-X similar tools. I believe Microsoft is offering decent tools compared to their more direct competition, but I'm yet to see something that makes me curious enough to really try them. I'm exceedingly happy with my current Python based stacks and curious about Go. I'd love to find a good reason to dig deeper into Ruby and Clojure, but, when it comes to Microsoft or C#, the move doesn't seem worth it. Not only because of the technology, but you have to change the whole stack, from server OS to developer desktop and deal with their idiosyncrasies.
You mentioned you used "Assembly, Turbo-C, Turbo-Pascal, Borland C++, Java, Javascript, Perl and many, many others", and, apart from JavaScript, none of them is closely associated with modern non-Microsoft development. I initially questioned you about it because, like myself, lack of knowledge of other options may hinder your ability to clearly assess a given technology's advantages.