Acme-CPANModules-Import-CPANRatings-User-perlancar
view release on metacpan or search on metacpan
},
{
"class" : "Dist::Zilla::Plugin::ShareDir",
"name" : "@Author::PERLANCAR/@Filter/ShareDir",
"version" : "6.030"
},
{
"class" : "Dist::Zilla::Plugin::MakeMaker",
"config" : {
"Dist::Zilla::Role::TestRunner" : {
"default_jobs" : 1
}
},
"name" : "@Author::PERLANCAR/@Filter/MakeMaker",
"version" : "6.030"
},
{
"class" : "Dist::Zilla::Plugin::Manifest",
"name" : "@Author::PERLANCAR/@Filter/Manifest",
"version" : "6.030"
},
name: '@Author::PERLANCAR/@Filter/ExecDir'
version: '6.030'
-
class: Dist::Zilla::Plugin::ShareDir
name: '@Author::PERLANCAR/@Filter/ShareDir'
version: '6.030'
-
class: Dist::Zilla::Plugin::MakeMaker
config:
Dist::Zilla::Role::TestRunner:
default_jobs: 1
name: '@Author::PERLANCAR/@Filter/MakeMaker'
version: '6.030'
-
class: Dist::Zilla::Plugin::Manifest
name: '@Author::PERLANCAR/@Filter/Manifest'
version: '6.030'
-
class: Dist::Zilla::Plugin::ConfirmRelease
name: '@Author::PERLANCAR/@Filter/ConfirmRelease'
version: '6.030'
href="https://metacpan.org/pod/Bencher::Scenario::Accessors::Set"
rel="nofollow">metacpan.org/pod/Bencher::Scenario::A...</a> .
<br><br>One drawback of using Mojo::Base and Object::Simple is its
similar but slightly different and incompatible syntax with the Moo*
family, so your code is not "upgradable" to Moo or Moose
once you need more features. And often you'll end up wanting them,
e.g. one day you'll probably read about the wonders of method
modifiers (before, after, around), or roles, or wanting to have a
lazy constructor, or triggers, and so on. <br><br>I'd recommend
instead Mo. It's more lightweight than Object::Simple and you can do
default value, builder, ro/rw, required, even coercion. But the
features are modular and you only pay for what you use. And once you
need more features later, you normally should be able to just
replace 'use Mo' in your code with 'use Moo' or 'use Moose'.
<br><br>Of course, this point is moot if you don't care about
compatibility/upgradability to Moo*.
Rating: 6/10
Test::Needs
Author: HAARG <https://metacpan.org/author/HAARG>
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
module Benchmark, I recommend looking at Benchmark::Dumb first
though. It has an interface like Benchmark (cmpthese() et all) but
with some statistical confidence.
Getargs::Long
Author: DCOPPIT <https://metacpan.org/author/DCOPPIT>
Nice idea, but some performance concerns. If you want to use
cgetargs (the compiled, faster version), you are restricted to the
getargs() interface, which only features checking for required
arguments and supplying default value. In which case you might as
well use Params::Validate directly as it's several times (e.g. 3-4x)
faster. <br><br>If you want to use the more featured xgetargs, there
is currently no compiled version. <br><br>All in all, I think users
should take a look at Params::Validate first.
Debug::Easy
Author: RKELSCH <https://metacpan.org/author/RKELSCH>
Not as easy as the name might claim. First of all, why do users need
to pass LINE explicitly for every call??? Other logging modules will
a file into a string" would need several modules and false
starts? Well, if you add encodings, Perl I/O layers, scalar/list
context, DWIM-ness, ... it can get complex and buggy. I'm glad there
are people taking care of this and making sure that a simple task
stays simple and correct.
File::Slurp
Author: CAPOEIRAB <https://metacpan.org/author/CAPOEIRAB>
Use the newer File::Slurper instead, which has a clearer API (e.g.
text vs binary, array/lines vs string) and encoding default. It's
arguably "saner" than File::Slurp and File::Slurp::Tiny.
<br>
File::Slurp::Tiny
Author: LEONT <https://metacpan.org/author/LEONT>
Use the newer File::Slurper instead, which has a clearer API (e.g.
text vs binary, array/lines vs string) and encoding default. It's
arguably "saner" than File::Slurp and File::Slurp::Tiny.
<br>
Perl::PrereqScanner::Lite
Author: MOZNION <https://metacpan.org/author/MOZNION>
A significantly faster alternative to Perl::PrereqScanner. It's
*almost* a drop-in replacement, there might still be some bugs in
missing detecting some modules, and you still have to do several
add_extra_scanner() calls like
devdata/perlancar view on Meta::CPAN
<img src="//cdn.perl.org/perlweb/cpanratings/images/stars-3.0.png" alt="***">
</h3>
<blockquote class="review_text">
I'd say in terms of footprint and runtime performance, this module is average (it's not the most lightweight nor the fastest pure-perl object system, not to mention against XS ones). See my Bencher::Scenarios::Accessors for a comparison, e.g. <a href...
</blockquote>
<div class="review_footer">
<p class="review_attribution">
<a href="/user/perlancar">perlancar</a> - 2016-06-23T07:18:10
(<a href="/dist/Object-Simple#12814">permalink</a>)
</p>
<div class="helpfulq">
devdata/perlancar view on Meta::CPAN
<img src="//cdn.perl.org/perlweb/cpanratings/images/stars-5.0.png" alt="*****">
</h3>
<blockquote class="review_text">
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...
</blockquote>
<div class="review_footer">
<p class="review_attribution">
<a href="/user/perlancar">perlancar</a> - 2015-10-16T07:19:20
(<a href="/dist/App-cpm#12284">permalink</a>)
</p>
devdata/perlancar view on Meta::CPAN
(<a href="https://metacpan.org/release/Getargs-Long/">1.1004</a>)
</h3>
<blockquote class="review_text">
Nice idea, but some performance concerns. If you want to use cgetargs (the compiled, faster version), you are restricted to the getargs() interface, which only features checking for required arguments and supplying default value. In which case you mi...
</blockquote>
<div class="review_footer">
<p class="review_attribution">
<a href="/user/perlancar">perlancar</a> - 2015-03-23T00:19:32
(<a href="/dist/Getargs-Long#12106">permalink</a>)
</p>
<div class="helpfulq">
devdata/perlancar view on Meta::CPAN
(<a href="https://metacpan.org/release/File-Slurp/">9999.19</a>)
</h3>
<blockquote class="review_text">
Use the newer File::Slurper instead, which has a clearer API (e.g. text vs binary, array/lines vs string) and encoding default. It's arguably "saner" than File::Slurp and File::Slurp::Tiny.
<br>
</blockquote>
<div class="review_footer">
<p class="review_attribution">
<a href="/user/perlancar">perlancar</a> - 2015-03-12T04:15:30
(<a href="/dist/File-Slurp#12082">permalink</a>)
</p>
devdata/perlancar view on Meta::CPAN
(<a href="https://metacpan.org/release/File-Slurp-Tiny/">0.003</a>)
</h3>
<blockquote class="review_text">
Use the newer File::Slurper instead, which has a clearer API (e.g. text vs binary, array/lines vs string) and encoding default. It's arguably "saner" than File::Slurp and File::Slurp::Tiny.
<br>
</blockquote>
<div class="review_footer">
<p class="review_attribution">
<a href="/user/perlancar">perlancar</a> - 2015-03-12T04:15:19
(<a href="/dist/File-Slurp-Tiny#12080">permalink</a>)
</p>
lib/Acme/CPANModules/Import/CPANRatings/User/perlancar.pm view on Meta::CPAN
package Acme::CPANModules::Import::CPANRatings::User::perlancar;
use strict;
our $AUTHORITY = 'cpan:PERLANCAR'; # AUTHORITY
our $DATE = '2023-10-29'; # DATE
our $DIST = 'Acme-CPANModules-Import-CPANRatings-User-perlancar'; # DIST
our $VERSION = '0.002'; # VERSION
our $LIST = {description=>"This list is generated by scraping CPANRatings (cpanratings.perl.org) user page.",entries=>[{description=>"\nI'm not sure this really "befits a ::Tiny distribution" just because it's a thin wrapper of something. P...
1;
# ABSTRACT: List of modules mentioned by CPANRatings user perlancar
__END__
=pod
=encoding UTF-8
lib/Acme/CPANModules/Import/CPANRatings/User/perlancar.pm view on Meta::CPAN
Cool. Now you can create your own Camel Code with ease!
=item L<Object::Simple>
Author: L<KIMOTO|https://metacpan.org/author/KIMOTO>
I'd say in terms of footprint and runtime performance, this module is average (it's not the most lightweight nor the fastest pure-perl object system, not to mention against XS ones). See my Bencher::Scenarios::Accessors for a comparison, e.g. <a href...
<br><br>One drawback of using Mojo::Base and Object::Simple is its similar but slightly different and incompatible syntax with the Moo* family, so your code is not "upgradable" to Moo or Moose once you need more features. And often you'll e...
<br><br>I'd recommend instead Mo. It's more lightweight than Object::Simple and you can do default value, builder, ro/rw, required, even coercion. But the features are modular and you only pay for what you use. And once you need more features later, ...
<br><br>Of course, this point is moot if you don't care about compatibility/upgradability to Moo*.
Rating: 6/10
=item L<Test::Needs>
Author: L<HAARG|https://metacpan.org/author/HAARG>
Nice. API is more convenient to use than Test::Requires, especially if you use subtests.
lib/Acme/CPANModules/Import/CPANRatings/User/perlancar.pm view on Meta::CPAN
<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
=item L<App::cpm>
Author: L<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...
<br>
=item L<Zodiac::Chinese>
Author: L<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>
lib/Acme/CPANModules/Import/CPANRatings/User/perlancar.pm view on Meta::CPAN
Author: L<DCOPPIT|https://metacpan.org/author/DCOPPIT>
Nice alternative module for benchmarking with a different interface than Benchmark (marking portion of code to be benchmarked with start and stop).
<br><br>For most Perl programmers familiar to the core module Benchmark, I recommend looking at Benchmark::Dumb first though. It has an interface like Benchmark (cmpthese() et all) but with some statistical confidence.
=item L<Getargs::Long>
Author: L<DCOPPIT|https://metacpan.org/author/DCOPPIT>
Nice idea, but some performance concerns. If you want to use cgetargs (the compiled, faster version), you are restricted to the getargs() interface, which only features checking for required arguments and supplying default value. In which case you mi...
<br><br>If you want to use the more featured xgetargs, there is currently no compiled version.
<br><br>All in all, I think users should take a look at Params::Validate first.
=item L<Debug::Easy>
Author: L<RKELSCH|https://metacpan.org/author/RKELSCH>
Not as easy as the name might claim. First of all, why do users need to pass B<LINE> explicitly for every call??? Other logging modules will get this information automatically via caller().
<br><br>Levels are a bit confusing: why is debug split to 2 (or 3)?
lib/Acme/CPANModules/Import/CPANRatings/User/perlancar.pm view on Meta::CPAN
Author: L<LEONT|https://metacpan.org/author/LEONT>
Who'da thought that something as seemingly simple as "slurping a file into a string" would need several modules and false starts? Well, if you add encodings, Perl I/O layers, scalar/list context, DWIM-ness, ... it can get complex and buggy....
=item L<File::Slurp>
Author: L<CAPOEIRAB|https://metacpan.org/author/CAPOEIRAB>
Use the newer File::Slurper instead, which has a clearer API (e.g. text vs binary, array/lines vs string) and encoding default. It's arguably "saner" than File::Slurp and File::Slurp::Tiny.
<br>
=item L<File::Slurp::Tiny>
Author: L<LEONT|https://metacpan.org/author/LEONT>
Use the newer File::Slurper instead, which has a clearer API (e.g. text vs binary, array/lines vs string) and encoding default. It's arguably "saner" than File::Slurp and File::Slurp::Tiny.
<br>
=item L<Perl::PrereqScanner::Lite>
Author: L<MOZNION|https://metacpan.org/author/MOZNION>
A significantly faster alternative to Perl::PrereqScanner. It's I<almost> a drop-in replacement, there might still be some bugs in missing detecting some modules, and you still have to do several add_extra_scanner() calls like $scanner->add_extra_...
<br><br>
( run in 0.468 second using v1.01-cache-2.11-cpan-0a6323c29d9 )