On the one hand, I've switched to Module::Build. Why? Simple - it's way easier to wrap my head around. It's one thing to complain that the users aren't getting the features they want, but I mean, if I can get my own modules out onto CPAN faster, aren't they really getting more than they would were I forced to use MM? When large numbers of people simply install to their perl distribution, why isn't MB good enough even as it is today?
On the other hand, schwern needs to learn a bit about communication. He's doing a huge disservice to his own body of work by the way he expresses himself. I can understand that having to continually defend the choice not to support a behaviour in another product which he thinks is a bad behaviour in the first place can be frustrating. But you can vent without degrading your audience. It is possible. Politicians do it all the time.
In some ways, I think schwern has become the kerfuffle, deflecting criticism (whether warranted or not) over lack of PREFIX support. That type of deflection makes it feel like he doesn't have any leg to stand on, so he has to deflect it. I say this even though when I wrote my Automated module install script, I had to do things a bit differently between Makefile.PL and Build.PL. I didn't find it onerous at all. Unfortunate, but not onerous. My bigger issue is still trying to get my IT support to install nmake on all affected Windows machines. Way too much red tape when we normally use gnumake everywhere. At least with MB, I can install my pureperl modules reliably, without relying on people who do not have the same priorities as I do.
In reply to Re: Why Module::Build?
by Tanktalus
in thread Why Module::Build?
by Ovid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |