view release on metacpan or  search on metacpan

README  view on Meta::CPAN

NAME
    Acme::CPANModules::Import::CPANRatings::User::davidgaramond - List of
    modules mentioned by CPANRatings user davidgaramond

VERSION
    This document describes version 0.002 of
    Acme::CPANModules::Import::CPANRatings::User::davidgaramond (from Perl
    distribution Acme-CPANModules-Import-CPANRatings-User-davidgaramond),
    released on 2023-10-29.

DESCRIPTION
    This list is generated by scraping CPANRatings (cpanratings.perl.org)
    user page.

    This list is generated by scraping CPANRatings (cpanratings.perl.org)
    user page.

ACME::CPANMODULES ENTRIES
    Perl6::Say
        Author: CHORNY <https://metacpan.org/author/CHORNY>

        Ok, it's not 2004 anymore, I suggest we retire or start to deprecate
        this module? This module now requires Perl 5.8, and Perl 5.10+ has
        &quot;say&quot; built in, so basically this is a module specifically
        for 5.8 *only*.

        Rating: 4/10

    Data::Rmap
        Author: BOWMANBS <https://metacpan.org/author/BOWMANBS>

        I was looking for a simple way to transform all DateTime objects in
        my data structure into string (e.g. &quot;2010-07-06&quot;). After
        failed experiment with Data::Walk and dumping Data::Transformer due
        to unsightly interface, I found Data::Rmap. It's straightforward to
        choose. <br><br>My only complaint would be the name: it's not
        immediately searchable (I was searching for 'data modify', 'data
        walk', 'data traverse', 'modify data inplace', and the like). Also,
        the name &quot;map&quot; suggests that the function will return a
        copy of the data (like Perl's builtin map) instead of modifying
        inplace.

    Data::Walk
        Author: GUIDO <https://metacpan.org/author/GUIDO>

        Nice interface (the analogy to File::Find certainly helps) and very
        straightforward to use, but one thing I can't do is modify the data
        inplace. I spent about an of hours trying to make Data::Walk do
        inplace modification, but finally gave up and use Data::Rmap
        instead.

        Rating: 8/10

    Data::Transformer
        Author: BALDUR <https://metacpan.org/author/BALDUR>

        Frankly, I don't like the interface. I suspect most people would
        like to just specify one callback function instead of one for each
        type. Also I don't like having to work with $$_ ($_ should perhaps
        be aliased to the real data). As the Data::Transformer's POD also
        said, those looking for alternatives can checkout Data::Walk and
        Data::Rmap, which I recommend instead. <br>

        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 &lt;leftop&gt; and &lt;rightop&gt;. 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: &quot;Have you the time to
        do this Damian?&quot; 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 &quot;blocks&quot;, this module
        doesn't really count block usage like the Unix &quot;du&quot;
        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 &quot;du $file&quot;'
        command for now. <br>

        Rating: 4/10

    DateTime
        Author: DROLSKY <https://metacpan.org/author/DROLSKY>