Acme-CPANModules-Import-CPANRatings-User-perlancar
view release on metacpan or search on metacpan
Dist::Zilla::Plugin::ReadmeFromPod
Author: FAYLAND <https://metacpan.org/author/FAYLAND>
Has some problems, e.g. it uses InstallTool phase so it conflicts
with DZP:StaticInstall when wanting to produce a static install
distro. Use alternatives like the simpler DZP:Pod2Readme or the more
complex DZP:ReadmeAnyFromPod. <br>
Rating: 2/10
Dist::Zilla::Plugin::Hook
Author: VDB <https://metacpan.org/author/VDB>
Great for debugging. Just whip up some code in dist.ini to e.g. dump
& print some stuffs, etc.
File::Tail::Dir
Author: JJSCHUTZ <https://metacpan.org/author/JJSCHUTZ>
Interesting features, but mooseware.
Rating: 6/10
Algorithm::Dependency
Author: ETHER <https://metacpan.org/author/ETHER>
Happily returns result when graph is cyclic (and thus proper
topological sorting cannot be done). See also Data::Graph::Util for
a simpler alternative. <br>
Rating: 6/10
Data::Match
Author: KSTEPHENS <https://metacpan.org/author/KSTEPHENS>
(Reviewing Sort::Topological, which is included in Data-Match
distribution at the time of this review). <br><br>Hangs when given a
dependency like: a => ["a"]. Happily returns result
when graph is cyclic (and thus proper topological sorting cannot be
done). See also Data::Graph::Util for alternative. <br>
Rating: 4/10
File::Find::Wanted
Author: PETDANCE <https://metacpan.org/author/PETDANCE>
File::Find lacks the "making easy things easy" part, so
modules like this are great. A further step would be an option to
omit $wanted for even simpler cases, but that would probably break
the interface. Another alternative is File::Finder, but it forces OO
style. <br>
Rating: 8/10
Hash::MD5
Author: MZIESCHA <https://metacpan.org/author/MZIESCHA>
Since this is essentially md5(dump($data)), why restrict yourself to
hash? This works also for any kind of Perl data structure.
DateTime::Format::Docker
Author: MZIESCHA <https://metacpan.org/author/MZIESCHA>
Isn't this basically ISO8601 (see DateTime::Format::ISO8601)?
WWW::CPANRatings
Author: CORNELIUS <https://metacpan.org/author/CORNELIUS>
To get the ratings for a single distribution, this client library
needs to download /csv/all_ratings.csv (~80KB at the time of this
writing) first. This is not the fault of the client because the
website indeed does not provide the necessary ratings data on the
/dist/:DISTNAME page. The client library should perhaps cache the
CSV response though. The implementation could also be simplified by
using slimmer libraries for this simple scraping task. But other
than that, does what it says on the tin.
Rating: 8/10
Parse::CPAN::Ratings
Author: LBROCARD <https://metacpan.org/author/LBROCARD>
Not as useful as the name implies. It requires you to download the
CSV of all ratings first, which BTW does not seem to be advertised
on the CPAN Ratings website. The CSV file only contains numeric
ratings and does not include any reviews. So basically what this
module does is just filter the CSV rows for a distribution's rating.
<br><br>One might want to look at WWW::CPANRatings instead.
Rating: 6/10
Acme::Curse
Author: MORITZ <https://metacpan.org/author/MORITZ>
This pure-perl module creates a shallow copy of the object instead
of directly removing blessing from the same object (which requires
XS). Acme::Damn is the more direct counterpart of bless(). <br>
Digest::SHA1
Author: GAAS <https://metacpan.org/author/GAAS>
Use Digest::SHA instead. In general, there is no reason in using
Digest::SHA1 over Digest::SHA. The latter is a core Perl module,
more updated, and implements the other algorithms while the former
only implements SHA-1 which is now deprecated. <br><br>
File::Checksum
Author: KNORR <https://metacpan.org/author/KNORR>
The "checksum" (basically just adding 16-bit words) is too
simplistic to be a real checksum or to be practically useful. Even
MD5 or CRC32 is infinitely better. <br>
WordPress::XMLRPC
Author: IGIBBS <https://metacpan.org/author/IGIBBS>
Still works, partially, but in general out of date. For example, to
get post the deprecated metaWeblog.getPost API method is still used
instead of the newer wp.getPost call (which understandably is only
introduced in WordPress 3.4, while this module is last updated with
WordPress 2.8.4). And apparently wordpress.com doesn't return
post_content anymore when you use metaWeblog.getPost.
<br><br>Luckily, performing XMLRPC request directly is easy enough.
Just use XMLRPC::Lite and peruse the Wordpress documentation here:
( run in 0.473 second using v1.01-cache-2.11-cpan-5b529ec07f3 )