Acme-CPANModules-Import-CPANRatings-User-perlancar
view release on metacpan or search on metacpan
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:
<a href="https://codex.wordpress.org/XML-RPC_WordPress_API"
rel="nofollow">codex.wordpress.org/XML-RPC_WordPress...</a>
Text::Levenshtein::Flexible
Author: MBETHKE <https://metacpan.org/author/MBETHKE>
My new favorite Levenshtein distance module. It's as fast (if not
faster) than Text::Levenshtein::XS and can provide a speed boost if
you don't care about distances above a certain limit. Which I think
in many cases is true.
CPAN::Changes
Author: HAARG <https://metacpan.org/author/HAARG>
Great and all, but one drawback is that it currently destroys
original file's formatting in serialize().
Module::Changes::ADAMK
Author: ADAMK <https://metacpan.org/author/ADAMK>
Any module from ADAMK should be interesting, including this one. But
please take a look at CPAN::Changes for the de facto standard
nowadays.
Module::Metadata::Changes
Author: RSAVAGE <https://metacpan.org/author/RSAVAGE>
Like Module::Changes, this module also tries to use a more defined
format for Changes. Sadly, it has not caught on. Please also take a
look at CPAN::Changes which seems to be the de facto standard
nowadays.
Module::Changes
Author: MARCEL <https://metacpan.org/author/MARCEL>
In general I'm not opposed to the idea of this module. The included
'changes' script is also pretty cool (which I'm trying to recreate,
for CPAN::Changes). <br><br>Just pointing out that I believe this
module has not really "caught on" among the CPAN
community. What has, is, CPAN::Changes which is followed by many
authors and even employed on MetaCPAN. <br>
Archive::Tar::Wrapper
Author: ARFREITAS <https://metacpan.org/author/ARFREITAS>
Sadly there is not a single perfect Archive::Tar::* module out
there. Either a module offers incomplete API, (was) buggy, or it is
crippled/limited in some way. Plus, the modules are mostly
incompatible with one another. And that's why TIMTOWTDI. <br><br>For
the task of just listing files in an archive, for example, it seems
only Archive::Tar and Archive::Tar::Wrapper are usable.
Archive::Tar::Wrapper is fast (because it utilizes external C-based
tar utility) and does not load all contents of an archive into
memory, but requires writing to temporary files and of course
requires a tar utility so portability to non-Unix systems might be
an issue.
Archive::Tar
( run in 1.209 second using v1.01-cache-2.11-cpan-ceb78f64989 )