You can find the most recent version of this tutorial here.
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.
This update has seen a LOT of changes since _03/_04, but the main ones are
- 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
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:
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:
$ cat sparrowfile
task => 'install my packages',
plugin => 'package-generic',
parameters => %( list => 'git-core carton cpanminus' )
task => 'install psgi app',
plugin => 'perl-app',
parameters => %(
'app_source_url' => 'https://github.com/melezhik/web-app.git',
'git_branch' => 'master',
'http_port' => 3030
All it does is:
- installing some packages required for further deployment ( git, cpanm, carton )
- installing perl5 psgi application by fetching source code from remote repository, installing dependencies with cpanfile/carton and running service using Ubic and Starman.
Here we go. On my vagrant Ubuntu 14.04 Trusty box I will have:
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.
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.]