They said they provide accounts to all CPAN authors, ... and most CPAN authors aren't interested.
Man, (and you've gotta be a man), be a hero and go green. You could save the world a gob load of natural resource by supplying your local power station with those chips off your shoulders.
If MS had suggested that they would only supply accounts to those CPAN authors that had shown an interest in supporting their modules on windows, you'd be up in arms. If they'd constrained it to only those modules that made special use of windows facilities, you'd be up in arms. They say: "Anyone who wants to", and you're still up in arms.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
Just because the module doesn't use XS, doesn't mean it'll work on Windows. I've got a module that doesn't work, because it deals with making a system() call to start another process, and I haven't gotten around to testing it on Windows. This could get useful...
If nothing else, that's a huge amount of resources MS is putting forward.
Even if you do your best to follow the rules and code portably, you still need to *test* your code on any weird platforms you care to support - such as Windows - just to make sure that you *did* follow all the portability rules and not miss anything. And there are plenty of cases where, to make your code portable, you need to write just a few lines of OS-specific code. There's at least two of my modules - neither of which uses XS, by the way - for which I will find this very useful.
Sure, I could just run Windows in a virtual machine, but that requires an expensive Windows licence, and that I know how to run Windows securely, which I don't.