All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Lots of comments! The articles that get discussion always surprise me. No one cared that I did my best to kick Solaris in the nuts over and over again, and no one has any thoughts on data homelessness, which I thought was an interesting topic. But that's okay.

As usual, people veered into the minutia rather than running with the topic. Some people were concerned about me having problems with par (I should have been more clear that it was the deprecated Par::Filter::Bytecode module to blame). Others were concerned about the attack on ActiveState (which was just part of the compiler woe drama despite the name of the article).

The appeal to group-think came not in a request forhelp with par, for help with ActiveState's site, but for which language the project should have been started in. Someone suggested Tcl which reportedly compiles nicely; Java got more support than would be expected here (diversity is good); someone suggested par without the filter or with the cyrpto filter as meeting the requirements (a good thought).

The articles that get discussion always surprise me. No one cared that I did my best to kick Solaris in the nuts over and over again, and no one has any thoughts on data homelessness

It's use Perl;, after all. Or maybe you just timed your post right so that it appeared at the top of the list of recent blogs at the optimum time. Or maybe those who replied first happen to have lots of Friends, who then saw their comments. Or your words had a blogelectic-fit inducing pattern in them.