- Website: www.byte-me.org
- About: Singer, dad, nerd, not necessarily in that order. @bytemeorg
- Posted Dear Perl lazyweb: how to construct read-only data objects out of JSON? to Mark Allen
Posted What about HTML to Markdown? to Mark Allen
Neil Bowers released a survey of markdown to HTML formatters recently. I thought it was an interesting coincidence, because I have recently written a CPAN library to go the opposite way,…
Commented on Why I use cpanfile (and you should too)
@miyagawa: I meant that git clone https://github.com/mrallen1/perl-Tombala && cd perl-Tombala && cpanm --installdeps . works But that it is awesome if cpanm https://github.com/mrallen1/perl-Tombala will work in the future....
Posted Why I use cpanfile (and you should too) to Mark Allen
CPANfile is a simple way to declare your project's dependencies in a build system independent manner.
- In recent versions of cpanminus, it makes your entire project installable from a git repository, and,
- it also allows you to "pin" your dependencies on a specific …
- Posted Steal this for Perl hackathons to Mark Allen
Commented on Thank You For Supporting Pinto!
Thanks Jeff. That's incredibly generous....
Commented on Introducing Net::EC2::Tiny
@steven It's an admirable goal to strive for, but there are several ::Tiny modules which have non-core dependencies. That being said, I could easily revert the Moo and the URI::Escape portions of the code, but once you opt for SSL...
Posted Introducing Net::EC2::Tiny to Mark Allen
One of the fun / cool things about Perl is that it can easily inhabit that space between "too complex for bash" and "too insignificant to invest in a C implementation." In my opinion a lot of the command line tools for EC2 are pretty terrible - they have a large learning curve, a high amount of…
Posted Pod::Perldoc at 3.19_01 to Mark Allen
One of the things that brian d foy worked pretty hard on for Perldoc inside of 5.16 was better UTF-8 support. We found that there are a huge number of variables for getting good Unicode support out of the "man" formatting pipeline. perldoc internally uses the "podulators" distribution to turn…
- Posted Net::Amazon::EC2 0.22 released; supports AWS v2 signatures to Mark Allen
Commented on I love Github
Actually, the hardest part about submitting this patch was finding the github repo name. :)...
- Posted Please help improve Pod::Perldoc 3.17 to Mark Allen
- Posted DistZilla from one newb to another to Mark Allen
Posted Exploit Git Hub tags! to Mark Allen
If you put your Perl code on Git Hub, I'd like to encourage you to use a a feature that isn't (at all) intuitive: tags.
Basic tags in git are a human friendly label that point to a certain commit. Basic tags don't have a git object associated with them so they're mostly for use on your loc…
- Posted Looking for Jeff Kim to Mark Allen
Commented on GitHub is an amazing service that much of the Perl community has...
Commented on Try the new perldoc
Thanks for the pointers! I have an experimetnal branch of Pod::Perldoc on github exploring the Pod::Text::* family https://github.com/mrallen1/Pod-Perldoc...
- Posted Writing API clients in Perl and Python to Mark Allen
Steven Haryanto commented on
GitHub is an amazing service that much of the Perl community has...
@perldreamer: Well said.
Besides, for public git repos it shouldn't matter which one you choose. They're sort of like offsite-backups. I've so far used github, bitbucket, gitorious, repo.or.cz, and it's just a matter of adding a couple of lines in your .git/config. But so far I'm most pleased with github (the attention to details in UI, the availability, the features). So go github!
Joel Berger commented on
Actually I think its a fine precedent to set/follow that ::Tiny modules (especially those ones for not so tiny tasks) pull in Moo.
::Tiny doesn't have a strict definition. Sometimes it mean literally "few lines of code" and sometimes it means "just the foundational bits you need to do some task". For those latter cases, yours included, Moo is probably fine. IMO
- Aristotle commented on Introducing Net::EC2::Tiny
Tatsuhiko Miyagawa commented on
Why I use cpanfile (and you should too)
I see, then you can do:
jakoblog.de commented on
Why I use cpanfile (and you should too)
I stopped editing Makefile.PL or Build.PL for both, CPAN modules and applications. With Dist::Zilla one can either track dependencies in dist.ini (also automatically with [AutoPrereqs]) or in cpanfile and use [FromCPANfile].
A benefit of this approach is a better separation between data ("what") and code ("how"): Makefile.PL and Build.PL is code how to do the build process. cpanfile is data to specify what dependencies exist.
blogs.perl.org is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.