blogs.perl.org

Well in my last post I added a few new attributes to my Database::Accessor::Element class and when playing about bout today I think I will have to revisit one of them 'aggregate'.

 has 'aggregate' => (
        is  => 'rw',
        isa => 'Str',
     );
 

So I am just going to bite the bullet and add in a 'Type' for this attribute so lets have a look at that.

This year I attended my fifth YAPC and, as usual, I’ve decided to reflect a bit on the venue, the talks, and the general mood.  Since I just did a (roughly) half-post in my date module series, I figured I’d go ahead and do another (roughly) half-post this week instead of waiting for next week.

I've been tooling around with a fun little app that I'm building on evenings and weekends. As part of that work I figured I'd let users authenticate via Runkeeper. Luckily Runkeeper uses OAuth2 and it's all pretty easy to get going with. I've published my very small contribution as Mojolicious::Plugin::Web::Auth::Site::Runkeeper

On a similar note, earlier this year I also released Mojolicious::Plugin::Web::Auth::Site::Spotify

If you're already using Mojolicious::Plugin::Web::Auth, then these modules will make it trivial for you connect with the Runkeeper and/or Spotify web services.

Read this article on Perl6.Party

DISCLAIMER: data theft is a serious crime in many jurisdictions. The author does not condone or encourage anyone to break laws. The information provided here is for educational purposes only.

Back when I wrote about exploiting operators made of invisible Unicode characters, a bunch of folks pointed out the module containing rogue code would actually have to be imported by the victim and it's not that easy to convince them. Fair enough. Today, we'll play a new game and crank it up a notch!

The Game Plan

We all worked on codebases that relied on a dozen of open-sourced modules, each of which relied on a few more, which in turn relied on... well, you get the point. Somewhere, a gazillion levels deep, there's some type of a leftpad in use that you never reviewed for sanity. Right?

So here's our setup:

So continuing on with the attribute fun today in the Moose-pen I am going to have a look at my 'Element' Database::Accessor class. So far like View there is not much to it only 'alias' and 'name'

has 'view' => (
        is  => 'rw',
        isa => 'View',
    );

As YAPC ... TPC::NA draws to a close, there was one final hurrah. About 25 (+/- a few) brave souls partook in the Wednesday Night Pull Request Challenge.

• 28 pull requests issued
• 4 modules release
• many more "person hours" spent coding, rewriting, and debugging
• 50 peoples worth of food eaten
• 1 budding cross-continental collaboration (App::DBCritic)
• a metric ton of community enjoyments had all around

Thank you to craigslist for sponsoring the event. And thank you to both the hard working YAPC organizers and PRC participants for coming together for something that I hope will become continued in the future.

I would be remiss if I did not greatly encourage anyone (no matter your skill level) to get involved in the monthly CPAN PRC Challenge run by Neil Bowers. It is his effort that gave me my first real opportunity to contribute to the Perl community through pull requests; but moreover it inspired me to take a role in introducing the fun to attendees of YAPC::NA::2016.

Do you like simple object system or lerge object system? I like simple object system.

In old days, I believed Perl would need complete object system, which has meta object protocol and class syntax.
Many perl programmers sought a good way to write object oriented programing.

A famouse lerge object system is Moose.
This module has many features, for example,
has, extends, with, is, isa, corce, dose, required, traits, builder, BUILD, DEMOLISH, etc.

A famouse simple object system is Mojo::Base.
This module is a part of Mojolicious.
Mojo::Base only has "has" method and a option to set default attribute value.

Do you know Mojo::Base was a little more complex at first?
Gradually, Mojo::Base removed the features except only really needed ones.

Mojolicious source codes is very clean. Mojolicious only use single inheritance and delegation.
Simple object system and single inheritance produce very clean codes.

I was surprised because I had believed Perl would need complete object system to produce good codes.

Hey everyone,

Following is the p5p (Perl 5 Porters) mailing list summary for the past week. Enjoy!

In yesterday's Moose-pen I hinted that I would be getting all my test in order. Well I did that and checked them in but there really was not that much to report on. Just a lot of repetitive code. I suppose I could write one test case to check all of my Database::Accessor classes using some simpler iteration over a list but I really like having a separate test case for all my classes as there really is only a small part that is common between them, so onto something different today.

I am going to start filling in the attributes of my various embedded Database::Accessor classes and I guess the best place to start in with Database::Accessor::View.

You can find the most recent version of this tutorial here.

Intro

When you suddenly get this brilliant idea, the revolutionary game-changer, all you want to do is to immediately hack some proof of concept to start small project flame from a spark of creativity. So I'll leave you alone for now, with your third mug of coffee and birds chirping first morning songs outside of the window...

...Few years later we meet again. Your proof of concept has grown into a mature, recognizable product. Congratulations! But why the sad face? Your clients are complaining that your product is slow and unresponsive? They want more features? They generate more data? And you cannot do anything about it, despite the fact that you bought the most shiny, expensive database server that is available?

Today I saw Damian Conway giving a talk at YAPC::NA 2016 (also known as The Perl Conference now :-). He was talking about some cool Perl 6 features, and I realized that some of them are available right now in Perl 5.

Reaching out to the Perl community at large due to this release being hardware-sensitive and feedback being most useful to me when it comes from many various hardware combinations, particularly if the graphics cards involved are older or stranger.

Please test this CPAN developers release on your platforms to confirm that
there are no regressions from the last stable release. ... Actually,
please do report any and all errors you can see, i am VERY keen to see
what other issues this throws up on different platforms.

• https://metacpan.org/release/MITHALDU/OpenGL-0.6704_05
• https://cpan.metacpan.org/authors/id/M/MI/MITHALDU/OpenGL-0.6704_05.tar.gz

This update has seen a LOT of changes since _03/_04, but the main ones are
these:

• updated and greatly automated compilation of hardware-dependent functions and constants
• enabled hardware feature detection for compilation on windows
• it even runs and tests successfully on a Win10 VM with OpenGL 1.1
• updated included freeglut.dll to latest release in major version 2

Update

Thanks to all the feedback i got, i was able to nail things down better and make a new dev release that should at least fix the glut regression:

https://metacpan.org/release/MITHALDU/OpenGL-0.6704_06

So today in the Moose-pen I am going to stub in the rest of my Database::Accessor classes and the rest of my Accessor.pm attributes.

• Param
• Condition
• Link
• Gather
• Filter
• Sort

 package 
           Database::Accessor::Param;
    use Moose;
    with qw(Database::Accessor::Roles::Base);
     has '+name' => ( required => 0 );
1;

Hi!

This is the very first ( to take it for a spin ) release of sparrowdo - a simple configuration management tool written on Perl6 and consuming sparrow plugins.

This is where Perl5, Perl6 could make a synergy. Consider a simple example of sparrowdo scenario:

Hey everyone,

Following is the p5p (Perl 5 Porters) mailing list summary for the past week. Enjoy!

Perl::Critic::Policy::Variables::ProhibitUnusedVarsStricter (whew!) is a Perl Critic policy that attempts to be more stringent about finding unused variables than the core policy of similar name. One of the things that has to be done to make this happen is to figure out which variables are interpolated into double-quotish strings.

The original version of this module had its own string-analysis logic, as do other Perl-Critic policies that have to figure out which variables are really being used. With the mainstreaming of postfix dereferencing, it seemed to me that the recognition of interpolated variables had become complex enough that a separate module to figure this stuff out was justified. Thus was born PPIx::QuoteLike.

[This is a post in my latest long-ass series.  You may want to begin at the beginning.  I do not promise that the next post in the series will be next week.  Just that I will eventually finish it, someday.  Unless I get hit by a bus.

IMPORTANT NOTE!  When I provide you links to code on GitHub, I’m giving you links to particular commits.  This allows me to show you the code as it was at the time the blog post was written and insures that the code references will make sense in the context of this post.  Just be aware that the latest version of the code may be very different.]

Last time I cleaned up most of the remaining CPAN Testers failures.  This time I’m getting ready for the first official release.  There isn’t a lot to talk about here, so this will be (uncharacteristically) a short entry in the series.

After encountering CodeNewbie at OSCON 2016 I've been thinking a lot about why there are so few new developers interested in Perl. I haven't been a Perl beginner for a very long time so I went looking for resources and found FAQ for the beginners mailing list. I wanted to know how active the mailing list was so I immediately went to the web achive. Reading through the list I saw things like:

"Is there a reason why you think one CPU is better than another?"

"your code exhibits many bad elements, and you don't seem to apply all the advice I've been giving you. Please go over http://perl-begin.org/tutorials/bad-elements/ , read it and internalise it."

Condescending, abusive advice is worse than no advice at all. There's no way I'd send a beginner into that. Nobody should have to learn like that. Seeing it ruined my afternoon. Maybe I should have read more of the FAQ:

"Who owns this list? Who do I complain to?"

This is a FREQUENTLY ASKED QUESTION?

If you do anything with 2 dimensional CNC machines such as plotters, mills, or lasers, you’ve probably used some form of vector graphics. The most popular open source vector graphics type is called SVG or Scalable Vector Graphics. If you’re doing this professionally, you need to know how to charge for that work, and if you know the length of the shapes included in that vector file, you can do a pretty good job of preparing an estimate for a customer. That’s where SVG::Estimate comes in. It does the mind melting math to tell you the length of arbitrary lines and shapes inside a vector file. 

[From my blog.]