http://preshing.com/20110822/p... http://preshing.com/20110926/h...

You mean books like Perl Best Practices?

Encourage? You fill up your shopping cart also while standing in the check-out line? It's the programmer who decides what to (ab)use.

Like OMG! http://preshing.com/20131219/b...

The language is called Perl. Funny that so many people on Slashdot still don't get it right.

Those things are happening or planned except for the version number change.

Tweaks to make complex data structures less of a nightmare: http://search.cpan.org/dist/pe...

better integrate the object model: https://github.com/stevan/p5-m...

Same here. I am a freelance Perl programmer and for the past 12+ months have been very busy with coding in ... Perl. More so than when Perl was considered the "glue that holds the web together". And no, it isn't maintenance of old code.

A number of people who left Perl and declared it dead are the ones that couldn't program in Perl to begin with (never learnt the language, thought it could be learned by trial and error), and most likely still can't in whatever they consider fashionable right now.

My disaster plan is keeping track of each apt-get install xxxxx and write down how I configured what I installed afterwards. And then there are still surprises, like how Apache changed its defaults going to 2.4 (IIRC). It's a lot more work compared to install new version and rsync -avh from backup, but all those notes I keep come in handy when I have to install something for a customer in a VM, etc.

Ah, yeah, should. In my experience the safe way, however, is to have taken notes during the previous install, doing a fresh install, and install and configure everything using those aforementioned notes (which now and then requires some research to get it right due to changes, and hence updating notes). Of course photos, movies, music, etc. can be safely restored from backup.

More like alphas. At least at the desktop.

A 3 year old can build a LEGO car following instructions in a booklet. An older child can cook something using a recipe. Both are examples of non-code representations of algorithms.

Still sounds like too much effort for too little profit. YMMV, of course.

And you would all do that for just a buck?

Best joke posted to Slashdot this month, thank you!

Thanks, for the clear explanation. It's extremely confusing to put it nicely.