Ok, that title is a bit of a teaser. But I do think that code should be sexy. In this full-color high-definition world, we've come to expect things to actually look attractive.
I'd love to see pretty logos or icons for each module on MetaCPAN. Perhaps we could add a new attribute to the META spec that points to an image file inside the distribution, or a URL somewhere.
What is the favorite module you have released to CPAN? For me, its not some shiny CMS or fancy scientific simulation. In fact, mine is probably horribly inefficient, maybe even a little evil, but I like this one best because it is clever.
Today I used my favorite of my modules in order to accomplish a difficult task, and in doing so I found a little bug, which I have just fixed. Which one is it? Let me introduce you to Tie::Array::CSV.
So, I went to Cluj.pm's anniversary meeting this month. It's been a year since Cluj.pm was formed and I've been lucky enough to be invited to the event. Here's my report of it.
I have written a few articles and more than a few essays for school/class. I know most of the major citations styles (MHRA, MLA, Chicago, etc.). Mostly, however, I use biblatex to format them all. However, I have begun to think that most of these citation styles are really just pointers to other resources or more generally they are really just URLs with a arcane special formatting rules. Many academics are obsessed with these bits of meta-data as they validate that the writer knows the rules of the road. When I read academic articles or books, I generally don’t notice or skip over citations as, while they are necessary and useful, they don’t always help with digestion of the actual argument. Although, occasionally in fields I know well, I will scan the citation to see who they are referencing just for credibility purposes.
I used to feel the Perl core should be as small as possible. That is, it should ship with the smallest number of modules whilst still being "practical". For everything else, there is CPAN.
So naturally, I was pretty pleased when I heard that CGI and some other modules were going to be removed from the core in perl 5.20. But lately, I've started to change my view on that. Here is why...
plenv is so cool that I'd like to use it for my personal project. Then, I have to hack up chef cookbooks for automated provisioning. I tried to write Chef LWRPs for the first time.
I'm looking for nominations for the 2013 White Camel Awards, and this year I'm using MobRater, a PlainBlack service, to get those nominations at http://whitecamelawards.mobrater.com.We're looking for people who have made significant non-technical contributions to Perl and the Perl community. We typically divide that up into user groups, community, and advocacy, although the categories are a bit squishy.
Us using MobRater doesn't mean that the most voted nomination will get the award, but the committee will certainly take that into account. There might be a great nomination that comes in at the end and doesn't get that many votes. To help get around that, check back sometime to vote on the new people added.
You can vote on the names there and also add your own. I'm really looking for new names, especially in the communities that might not overlap that well with the US and European communities that I knew much better. So far, we've had no one from India or Africa receive an award, and we've had very few recipients from Asia and South America. There might be people doing great things for their local communities that don't get much press far away.
This is a collection of ideas for how we can encourage bloggers using blogs.perl.org to split their posts into an abstract and body. Attempts at education have largely failed, so I think we should try something else.
Food for thought, if we update our Modules, don't we want our users to use the current version, so should we not by default do the same with others Modules. Thus we always show the current version number, regardless.
Now able to show dual-life modules current version number.
Lets start with the changes and inspiration.
Switched to using MetaCPAN-API due to a write issue with CPAN, neilb++
Switched to using Perl-PrereqScanner to do most of the grunt work as pointed out
by Mithaldu++ daxim++
spelling, re-factor option names, inspired by mauke++
--format change output format
changed default output, no extra processing, only distribution version
for modules without a version number mst++
if I missed anybody, sorry
And some new features.
Add command line option to show dual-line module versions as well.
midgen --dual_life
Add ability to read/write options from ~/.midgenrc
I've taken a lot of time off from the work force (and even more from the community). I have been occupying my time with pursuing other ventures (my other brand), but now I find myself actively desiring to write code.
So i began by refreshing and slightly expanding the "jeffa/unlocalhost" brand and ensuring all was available and secured. Next I grabbed the small amount of old code from my CPAN repository and rebuilt each distribution using Module::Starter. Not only did i upload each distribution to github, i also set up Jenkins on my server and set up a job for each one. Each Jenkins job clones a read-only copy, builds the make file, runs the tests (and creates JUnit output for Jenkins) and builds a tardist upon success.
Awesome. Not a bad first step if i do say so myself. And in the process of setting this up i was already able to correct some Pod::Coverage infractions. Next step will be to write proper tests for each of these distros but i am not going to spend too much more time on them. If others wish to fix bugs or otherwise enhance the code they now have a much cooler way to submit patches.
Uploading to rubygems is very simple, I don't know or use ruby, but just from looking at the frontpage I'm pretty confident that it would be pretty quick and easy : 1/2 of the main content of the page is a quickstart guide in 3 simple steps. Neat! (I'm sure there is more to writing a good gem, but that definately leaves you feeling confident to give it a go).
Uploading to cpan via PAUSE is something I do a couple of times a week without really thinking about it, that doesn't mean it's easy, it's pretty much muscle memory after a decade of doing it.
However, from the perspective of somebody outside the "echo chamber" (as I most certainly was when I looked at the rubygems site), it's very different when you arrive at the cpan.org site.
A short time after I posted a message about
XML-Grammar-Screenplay
to a Perl forum, a Perl enthusiast sent me a message reading like that:
I would think that a proper screenplay grammar would be useful (I've thought
of writing one myself). Though I've looked through your screenplay examples, I
can't see any of them, anywhere, which is actually rendered in correct
screenplay format (example),
nor anything which appears to directly support the special directives often
found in screenplays, such as sluglines. Am I missing something?
(Poor) Directions for formatting a screenplay are
here.
That really doesn't cover the *extremely* rigid formatting rules involved (a
reader can often toss a script with bad margins and get paid for it anyway).
Notes from a Newbie document the creation and deployment of yardbirdfanclub.org with Perl Catalyst on shared hosting. They are intended for a Perl Catalyst Newbie who would like to study the creation and deployment of a simple Perl Catalyst application.
On behalf of the PDL Porters, and especially our tireless leader Chris Marshall, I am very happy to share the news that PDL 2.006 has been released, I’m reposting the announcement here, find the full message including release notes on the mailing list. It even includes my first contributions to the PDL core :-) Enjoy!
The PDL development team is pleased to announce
the official release of PDL-2.006 and an updated
draft of the PDL Book to accompany its release.
Of specific note:
PDL VERSION numbers now use single decimal
format. This will be the standard going forward.
PDL now has three graphics options that build on
all supported PDL platforms (thanks to work by
Craig DeForest and David Mertens and a host of
others):
One of my problems related to Perl is that I'm not aware of a lot of things going on in the perl world,
and there isn't a single place I can go to try and keep up.
I suspect I'm not the only one. This post outlines an idea for a "perl community home page", where you could go to "keep up". I've whipped up a prototype, which is just a static page with a mashup of various feeds and static data.
So I noticed that CPAN is no longer king of the hill when it comes to sheer number of packages - rubygems took that title mid 2011 (when exactly depends on whether you include dev version and backpan which it lacks).
Rubygems had previously claimed the title based on dodgy numbers, but by the start of 2012 there really wasn't any doubt - that's a hell of a lot of uploaded code.
I looked into rubygems a bit to see just what was behind the massive explosion (admittedly still a bit in denial and looking for a smoking gun to explain), and found that it's a very very different kettle of fish.
That's a good thing for both ruby and perl - there's a lot that can be learnt from comparing and finding (and stealing, something both ruby and perl communities are both happy to do) good ideas.
In 1980, George Copeland wrote
an article
titled "What if Mass Storage were Free?".
Costs of mass storage were showing signs
that they might fall dramatically.
Copeland, as a thought exercise, took this trend to its extreme.
Among other things, he predicted that deletion would become
unnecessary, and in fact, undesirable.
Copeland's
thought experiment has proved prophetic.
For many purposes, mass storage is treated as if it were free.
For example, you probably retrieved this blog post from a server
provided to me at no charge, in the hope
that I might write and upload something interesting.
Until now languages were high-cost efforts.
Worse, language projects ran a high risk of disappointment,
up to and including total failure.
I believe those days are coming to an end.
1: Reversing camera switch.
- That is, a switch to lie to the display unit, telling it we are reversing, so the reversing camera displays without the car actually moving backward.
1.1: Disassemble dash to be able to get at the display unit’s wiring. DONE.
1.2: Put a connector inline to the existing wiring. Should hold wires securely, have no visible changes to the car when external things aren’t connected.
1.2.1: Decide upon, and buy connector: DONE. Have gone with a Molex Mini-Fit Jr, 20-pin. This is the same connector as ATX power supplies (without the extra 4-pin connector), so are reasonably easy to find in general-commercial-availablity.
1.2.2: Figure out how to connect the connector, in the car, without major disasembly, or melting bits of the car.
1.2.3: Do so, at least for 12 V (accessory or always-on?) and REV. Other lines can come later.