|There's more than one way to do things|
zentara thank you for your comment!
It sounds like you are a MSWindows promoter and are trying to alter Perl's development to suit Windows by taking away all the useful Unix tools ... how is that being cross-platform? Why should Unix/Linux developers give a damn about Window's problems?
No, I am NOT a MSWindows promoter! However in many cases I have been forced to use Windows and I am mainly a user of it. I want, as you, Perl to be cross-platform and I do not want to remove any thing!
Not all modules need to be portable between the different implementations of Perl. However I want it to be easy to develop a portable module. If you want to write portable code you need to consider the limitations of the Perl implementation in all the intended target systems. The current Perl documentation gives very little support to avoid non portable constructs. But even with good documentation many non portable function will been used by mistake. This is one of the reasons for my sometimes non realistic proposals.
When I started to use Strawberry Perl http://strawberryperl.com/ I got the possibility to install modules from CPAN. I was a big improvement for me. The downside was the difficulties to know which module can be used in Windows.
The Windows operating system seems to have less good resistance for programming errors. Installing some CPAN modules degenerate the Windows system and it has to be repaired. This is especially a problem running smoke test on Windows.
The fact that your system can be harmed by installing Perl modules, can and probably will, give Perl bad reputation.
So I believe Unix/Linux developers should give a damn about Window's problems at least when developing portable modules.