Acme-CPANModules-Import-CPANRatings-User-perlancar
view release on metacpan or search on metacpan
recipes in the cookbook currently don't really entice me to use the
module. Let's see: <br><br>1) batch file rename: it's much simpler
to use 'rename' or 'perlmv' utility. Or, it's much shorter to just
use plain perl like 'for (grep {-f} <*>) { rename $*,
s/.log$/.txt/r }'. <br><br>2) recursively remove a directory tree:
it's much shorter to just use 'File::Path::remove*tree()'.
<br><br>3) increment a counter file: no locking (it's classic 1990's
counter.cgi race condition all over again). Take a look at, for
example, The Perl Cookbook chapter 7.11. Or I think one of Randal
Schwartz's articles. <br><br>As an alternative, one can also take a
look at Path::Tiny.
Common::Routine
Author: PEKINGSAM <https://metacpan.org/author/PEKINGSAM>
A couple of comments: <br><br>* Some functions like min(), max(),
etc need not be reinvented because they are already in core module
List::Util. But I guess the author wants to be able to say
min([1,2,3]) in addition to min(1,2,3). <br><br>* round() uses
Number::Format, note that rounding number using this module is
hundreds of times slower than using sprintf(). <br><br>
Submodules
Author: ZARABOZO <https://metacpan.org/author/ZARABOZO>
A couple of prior arts: <br><br>* all, <a
href="https://metacpan.org/pod/all"
rel="nofollow">metacpan.org/pod/all</a> (since 2003), nicer
interface and offers "use"/compile-time interface, so it's
more equivalent to the statements it wants to replace. The
Submodules equivalent would be: BEGIN { for my $i
(Submodules->find("Blah")) { $i->require } }.
<br><br>* Module::Require, <a
href="https://metacpan.org/pod/Module::Require"
rel="nofollow">metacpan.org/pod/Module::Require</a> (since 2001),
also nicer interface, more flexible, and more lightweight
implementation. <br><br>I don't like Submodules' interface, it's too
verbose and clunky. IMO, the interface should be a one-liner and
without manual looping.
Regexp::Assemble
Author: RSAVAGE <https://metacpan.org/author/RSAVAGE>
I guess it depends on your data, but for random shortish strings
(hundreds to thousands of them), I find that using raw joining is
much faster to assemble the regex. And the resulting regex is also
(much) faster to match. Please see Bencher::Scenario::RegexpAssemble
if you're interested in the benchmark script.
Tie::Scalar::Callback
Author: DFARRELL <https://metacpan.org/author/DFARRELL>
There is a prior art Tie::Simple (created in 2004) which works for
scalar as well as the other types of ties that perl supports (array,
hash, handle). <br>
JSON::Create
Author: BKB <https://metacpan.org/author/BKB>
Review for 0.02: Performance-wise, still has some catching up to do
against JSON::XS & Cpanel::JSON::XS with regards to encoding
arrays & hashes. <br><br>UPDATE review for 0.19: Giving it 4
stars now. Speed has been improving and on-par/slightly better than
the other JSON XS modules in some areas, while a bit worse in some
other areas. Faster modules are always welcome.
Rating: 8/10
Set::Scalar
Author: DAVIDO <https://metacpan.org/author/DAVIDO>
Confirming previous reviewer, the module is a lot slower (~ 20-40x)
than other alternatives like Array::Utils or List::MoreUtils when
you want to perform basic set operations like
union/intersect/diff/symmetric diff.
Exporter::Easy
Author: NEILB <https://metacpan.org/author/NEILB>
I can see the value of Exporter::Easy (although these days the
saving in typing is not as big, with plain Exporter one can just
say: use Exporter 'import'; our @EXPORT = qw(a b c)).
<br><br>However I fail to see the value of Exporter::Easiest. I'd
rather use plain Perl than some DDL which cannot be checked
statically or cannot be syntax-highlighted, just to save some []'s
and ()'s (which I can get my editor to help me type them).
<br><br>In short, I'd rather use plain Exporter than save a few
keystrokes but add a non-core dependency.
Rating: 6/10
App::cpm
Author: SKAJI <https://metacpan.org/author/SKAJI>
Due to parallel processes and defaulting on no_test, can be several
times faster than cpanminus (tried installing a module on a vanilla
perlbrew instance with local CPAN mirror, which pulled +- 200
distributions, "cpanm -n" took 2m9s, while cpm took 38s.)
I hope this gets developed further. Great job. <br>
Zodiac::Chinese
Author: CAVAC <https://metacpan.org/author/CAVAC>
From the doc: "This module generates one's Chinese zodiac.
However, for those born in late January to early February, it may be
wrong." Well, a module that might return wrong results is not
very useful. <br>
Rating: 2/10
JSON::MultiValueOrdered
Author: TOBYINK <https://metacpan.org/author/TOBYINK>
I guess if you want to switch JSON implementation more easily with
JSON, JSON::PP, and JSON::XS, it's better to use
JSON::Tiny::Subclassable instead of JSON::Tiny, because the
interface is more similar to JSON{::XS,::PP}, although it's not
exactly the same. JT:Subclassable also supports pretty() which is
often used when debugging. In short, I found
JSON::Tiny::Subclassable is a better "Tiny JSON" module
than JSON::Tiny.
JSON::Tiny
Author: DAVIDO <https://metacpan.org/author/DAVIDO>
Ah, the many JSON implementation modules out there... <br><br>I
guess if you want to switch JSON implementation more easily with
JSON, JSON::PP, and JSON::XS, it's better to use
JSON::Tiny::Subclassable instead of JSON::Tiny, because the
interface is more similar to JSON{::XS,::PP}, although it's not
exactly the same. <br><br>
Devel::Confess
Author: HAARG <https://metacpan.org/author/HAARG>
Provides some more features compared to Carp::Always, like producing
stack trace even when exception is ref/object, color & dump
function arguments (so you don't need a separate Carp::Always::Dump
and Carp::Always::Color). Recommended. <br>
Carp::Always
Author: FERREIRA <https://metacpan.org/author/FERREIRA>
This module works well for string exceptions (e.g. die "some
message"), but for ref/object exceptions (e.g. die
[404,"Not found"] or die $some_object) it will simply
print/return the ref/object and thus no stack trace information is
produced. <br><br>See also Devel::Confess, which can handle
ref/object. <br><br>References: <br> <a
href="http://blogs.perl.org/users/graham_knop/2013/09/carp-always-ev
enobjects.html"
rel="nofollow">blogs.perl.org/users/graham_knop/2013...</a>
experimental
Author: LEONT <https://metacpan.org/author/LEONT>
Our prayer has been answered. experimental was added to perl core in
5.19.11
Exporter::Lite
Author: NEILB <https://metacpan.org/author/NEILB>
Mostly unnecessary. The main premise of this module is that you
don't need to inherit to use it. But you also can use Exporter (a
core module, BTW) without inherinting it: <br><br>use Exporter
qw(import); <br>
Date::Holidays
Author: JONASBN <https://metacpan.org/author/JONASBN>
The idea is good, but a couple of things prevents me from using this
interface. <br><br>First, the use of TryCatch (which brings the
Moose ecosystem) makes the startup overhead too high for my taste
(about 0.5s on my PC). Which is rather unfortunate because
Date::Holidays itself does not use Moose. <br><br>Second, the
interface assumes that a country has a single set of holidays, which
is too restrictive in some cases. A more flexible/general interface
would allow adding more calendars based not only on country but also
religion, special community, organization, etc. And allow adding
custom calendars. <br>
Furl
Author: SYOHEX <https://metacpan.org/author/SYOHEX>
@Kira S (I wish cpanratings adds a feature to comment on a review):
<br><br>Comparing WWW::Mechanize with Furl is not really
apples-to-apples, since Furl does not support parsing/following
links or form processing. As the Furl POD itself suggests, Furl is
( run in 0.484 second using v1.01-cache-2.11-cpan-5a3173703d6 )