Perl-Sensitive Sunglasses | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Keeping things "pure Perl" is a valid design constraint, but there's stuff that the vanilla base perl can't do that require external resources. Interfacing with native C libraries, for one instance, which already solve a particular problem pretty thoroughly (e.g. ImageMagick). Another reason why things aren't done in pure Perl is that often there's a speed advantage to manipulating things directly in C. They're a good idea because they work, they're tested, and they get the job done quickly. And with PAR you can distribute them fairly easily without worrying about the other side's configuration or dependencies or what not. So no you're not "wrong" to want to stick to pure Perl, you've just chosen to pay more attention to different constraints. Just be aware that there's other approaches and ways to avoid the downfalls you've noted.
The cake is a lie. In reply to Re: Have I misunderstood the point of modules or just CPAN?
by Fletch
|
|