We can all argue that adding Win32 features is poluting Perl, but I can't really agree. Now, they could fork Perl and produce an MS-only version, but would that be *so* bad? *If* this happened, then ActiveState would certainly continue to graft in any enhancements to the Perl core and hence users wouldn't lose anything much, except for perhaps a time delay, much like the one that we have now waiting for AS to give us a new build. It certainly can't affect Perl on other platforms since they can't directly affect the real Perl distribution, so all us Unix people are quite safe. Perl itself is not controlled by MS or ActiveState, so there's no way they can get total crap into *true* Perl.ĪctiveState always has, and will continue to, distribute a version of Perl that it has compiled, no doubt together with some new modules etc., but I don't really think this will change things too much. Of *course* they want to make Perl MS-proprietary if they can.
Now they're just doing exactly the same thing. Since then, things have been cleaned up a lot and Win32 is a well supported Perl platform, largely due to MS's original investement.
In doing so, a somewhat roughshod port & a set of new packages were created. The entire reason that Perl on Win32 exists in as good a form as it does is because Microsoft wanted to ship Perl in the NT Resource Kit a few years back, having recognized its importance, and hence paid for the port.
0 kommentar(er)
