Acme-CPANModules-Import-CPANRatings-User-davidgaramond
view release on metacpan or search on metacpan
Rating: 4/10
Data::Traverse
Author: FRIEDO <https://metacpan.org/author/FRIEDO>
I find the interface rather unintuitive, because I expect data to be
in $_ (instead of type). For those looking for alternatives, see
also Data::Walk (which provides breadth-first as well as
depth-first) and Data::Rmap (which provides inplace modification).
<br>
Rating: 4/10
Regexp::Grammars
Author: DCONWAY <https://metacpan.org/author/DCONWAY>
Parse::RecDescent is dead. Long live Regexp::Grammars! <br><br>As
Damian himself has said/presented, RG is the successor for the
popular PRD. <br><br>The docs of RG is not as complete (yet) as
PRD's. <br><br>The PRD grammar syntax is also nicer/cleaner (due to
RG having some restrictions because you are writing your grammar
inside a regex). <br><br>RG doesn't (yet) have some of the features
of PRD, like <leftop> and <rightop>. But it does have
most of the features, and add a few of its own. <br><br>RG performs
significantly faster than PRD. <br><br>In general, whenever you
consider PRD to be a good candidate of tool to solve your problem,
consider using RG. <br><br>But you need Perl 5.10+ to use RG, as it
depends on regex features not found in older Perl. <br>
Rating: 8/10
Parse::RecDescent
Author: JTBRAUN <https://metacpan.org/author/JTBRAUN>
Responding to previous comment from MB: "Have you the time to
do this Damian?" The answer is yes, in the form of
Regexp::Grammars, which Damian said himself is the successor of
Parse::RecDescent. <br><br>To give credit to this module, PRD is
very featureful and easy to use, it's very convenient to generate
parsers, and the docs is quite complete. The only problem with it
is, as many have pointed out, speed. <br><br>It is *seriously* slow,
with parser generation can take up to half a second on my laptop
with a moderate grammar (200-400 lines) and parsing can take seconds
even minutes for a moderately long string. It is orders of magnitude
slower than other parsers. Do think a few times before deciding you
can take the performance hit of PRD. <br><br>For alternatives, try
Regexp::Grammars. (Or Parse::Yapp or Parse::EYapp, as other
reviewers have written.)
Rating: 6/10
Test::Seperate
Sorry, just commenting the name, shouldn't it be Separate?
File::Size
Author: OFER <https://metacpan.org/author/OFER>
Frankly I prefer the name and interface of Filesys::DiskUsage.
Sadly, despite the docs mentioning "blocks", this module
doesn't really count block usage like the Unix "du"
command, because it doesn't take multiple hard links into account.
<br><br>Even more sadly, Filesys::DiskUsage doesn't either.
<br><br>I guess I'll have to do with 'system "du $file"'
command for now. <br>
Rating: 4/10
DateTime
Author: DROLSKY <https://metacpan.org/author/DROLSKY>
*THE* definitive date/time handling module in Perl (and even maybe
in all major programming languages). Can't believe I went through
all the pain of reinventing the wheel, and using various date/time
modules of various quality & interface. If only I had known
DateTime earlier. <br><br>Look no more, DateTime it is. <br>
Data::Rx
Author: RJBS <https://metacpan.org/author/RJBS>
I've been mulling over writing this kind of module (planning to call
it Schema::Nested or something), but never got around to do it.
Thankfully somebody stepped up and did it! Keep up the good work,
will be looking forward to future releases (especially i'm hoping
for some subclassing mechanism, for better reuse of schemas). <br>
DBI::Mysqlsimple
I agree with the previous reviewer. IMO, overall this module is not
necessary. Plain DBI is actually simple enough for simple cases.
Maybe the author of Mysqlsimple did not realize this. Let's compare:
<br><br>* Retrieving a single row: <br> Mysqlsimple: my ($v1,$v2) =
$db->get_row("select v1,v2 from table"); <br> DBI: my
($v1, $v2) = $dbh->selectrow_array("select v1,v2 from
table"); <br><br>* Retrieving a single row (with params): <br>
Mysqlsimple: my ($v1,$v2) = $db->get_row("select v1,v2 from
table where cond1=? and cond2=?", [$cond1,$cond2]); <br> DBI:
my ($v1,$v2) = $db->selectrow_array("select v1,v2 from table
where cond1=? and cond2=?", {}, $cond1,$cond2); <br><br>*
Retrieving all rows with params: <br> Mysqlsimple: my $rows =
$db->get_rows(..., [$param1, $param2]); <br> DBI: my $rows =
$dbh->selectall_arrayref(..., {}, $param1, $param2); <br><br>*
do() with params: <br> Mysqlsimple: my $rows = $db->do(...,
[$param1, $param2]); <br> DBI: my $rows = $dbh->do(..., {},
$param1, $param2); <br><br>As you can see, the differences are
minimal. <br>
Rating: 2/10
Carp::Always
Author: FERREIRA <https://metacpan.org/author/FERREIRA>
Modules like this deserve to be more well-known and should perhaps
included in core Perl (or even become a command-line switch). I'm
never comfortable with Carp and all the "complexity" of
using it. What I wanted is simple, when debugging I want all die()'s
(and perhaps warn() too, but much less often) to print a stack
trace. <br><br>Call me inflicted with Ruby- or Python-envy, but it's
been so ridiculous wanting to print out stack traces in Perl. I
don't want to have to change/rewrite all my die()'s to croak() or
confess()! And what about library codes which use die()?
<br><br>Thank God somebody wrote Carp::Always.
Data::Dump
Author: GARU <https://metacpan.org/author/GARU>
I've envied Ruby users which can use just "p" to print out
data structures instead of us which used to have to do 'use
Data::Dumper; print Dumper(...);'. And even then there's this '$VAR1
= ' garbage which 99% of the time is not wanted. Which often makes
me wonder, shouldn't P in Perl stand for Practical? <br><br>With
Data::Dump we're still a bit behind but closer. One rant is the with
the doc: the pp() function should perhaps be advertised more
prominently, since I suspect that's what most users want most of the
time.
V Author: ABELTJE <https://metacpan.org/author/ABELTJE>
What a nice little module. It is by far the easiest to review ;-)
<br><br>I have been using my own little script called
"pmversion" which serves the same exact purpose. I guess
I'll be using V from this moment on. It's amazing doing something as
basic as showing a module's version had not been this easy or even
easier. <br>
Test::Unit
Author: MCAST <https://metacpan.org/author/MCAST>
Test::Unit is of course a fine module. But if you are shopping
around for testing framework, I recommend you try Test::Class
instead, which combines the best of two worlds. First, you get xUnit
style, but I think with a slightly simpler interface. Second, you
get to use all the standard Perl testing stuffs like Test::Simple,
Test::More and Test::Harness. This is better because it's what most
Perl modules use (so you might be more familiar with it if you're a
Perl programmer), plus there are more kinds of "assert"
functions in Test::More and friends compared to Test::Unit::Assert.
Rating: 8/10
Module::Build
Author: LEONT <https://metacpan.org/author/LEONT>
Here's the short story: first there's Exutils::MakeMaker, which
requires make and hard to extend, but everybody uses it due to lack
of alternatives. Then came Module::Build which is pure perl and
easier to use for authors, but breaks compatibility. Users can no
longer use the 'perl Makefile.PL && make && make
install' mantra. Plus, it used to not support PREFIX. Plus, MB-based
modules require MB which is not by default installed. This pisses *a
lot* of people. <br><br>Lesson to learn: maintaining
backward-compatibility is very important, especially for end users.
I think the intention of MB is a good one, but the execution could
be a bit better. For example, perhaps the "Build.PL"
script could've still just been named "Makefile.PL",
couldn't it? <br><br>I recommend people shopping for a module
installer to look at Module::Install instead. MI is a middle ground
between Eu::MM and MB. It's pure perl and easy to extend but it also
allows users (and CPAN.pm et al) to install modules the old way. It
embeds a copy of itself in every MI-based modules, so there's no
depedency hell. Best of both worlds.
Rating: 6/10
YAML::LibYAML
Author: INGY <https://metacpan.org/author/INGY>
It's about time Perl gets a complete and proper YAML parser. This is
it. In the past I've been bitten by a couple of YAML's and
YAML::Syck's minor bugs, in addition to several crashes (don't know
how they are recently). But using YAML::XS (YAML-LibYAML) I get the
feeling, for the first time, of a first class parser comparable in
stability and completeness to that in Ruby and Python.
FAQ
What is an Acme::CPANModules::* module?
An Acme::CPANModules::* module, like this module, contains just a list
of module names that share a common characteristics. It is a way to
categorize modules and document CPAN. See Acme::CPANModules for more
details.
What are ways to use this Acme::CPANModules module?
Aside from reading this Acme::CPANModules module's POD documentation,
you can install all the listed modules (entries) using cpanm-cpanmodules
script (from App::cpanm::cpanmodules distribution):
% cpanm-cpanmodules -n Import::CPANRatings::User::davidgaramond
Alternatively you can use the cpanmodules CLI (from App::cpanmodules
distribution):
% cpanmodules ls-entries Import::CPANRatings::User::davidgaramond | cpanm -n
or Acme::CM::Get:
% perl -MAcme::CM::Get=Import::CPANRatings::User::davidgaramond -E'say $_->{module} for @{ $LIST->{entries} }' | cpanm -n
or directly:
% perl -MAcme::CPANModules::Import::CPANRatings::User::davidgaramond -E'say $_->{module} for @{ $Acme::CPANModules::Import::CPANRatings::User::davidgaramond::LIST->{entries} }' | cpanm -n
This Acme::CPANModules module also helps lcpan produce a more meaningful
result for "lcpan related-mods" command when it comes to finding related
modules for the modules listed in this Acme::CPANModules module. See
App::lcpan::Cmd::related_mods for more details on how "related modules"
are found.
HOMEPAGE
Please visit the project's homepage at
<https://metacpan.org/release/Acme-CPANModules-Import-CPANRatings-User-d
avidgaramond>.
SOURCE
Source repository is at
<https://github.com/perlancar/perl-Acme-CPANModules-Import-CPANRatings-U
ser-davidgaramond>.
SEE ALSO
Acme::CPANModules - about the Acme::CPANModules namespace
cpanmodules - CLI tool to let you browse/view the lists
AUTHOR
perlancar <perlancar@cpan.org>
CONTRIBUTOR
Steven Haryanto <stevenharyanto@gmail.com>
CONTRIBUTING
To contribute, you can send patches by email/via RT, or send pull
requests on GitHub.
Most of the time, you don't need to build the distribution yourself. You
can simply modify the code, then test via:
% prove -l
If you want to build the distribution (e.g. to try to install it locally
on your system), you can install Dist::Zilla,
Dist::Zilla::PluginBundle::Author::PERLANCAR,
Pod::Weaver::PluginBundle::Author::PERLANCAR, and sometimes one or two
other Dist::Zilla- and/or Pod::Weaver plugins. Any additional steps
required beyond that are considered a bug and can be reported to me.
COPYRIGHT AND LICENSE
This software is copyright (c) 2023 by perlancar <perlancar@cpan.org>.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
BUGS
Please report any bugs or feature requests on the bugtracker website
<https://rt.cpan.org/Public/Dist/Display.html?Name=Acme-CPANModules-Impo
rt-CPANRatings-User-davidgaramond>
When submitting a bug or request, please include a test-file or a patch
to an existing test-file that illustrates the bug or desired feature.
( run in 1.038 second using v1.01-cache-2.11-cpan-5a3173703d6 )