Recently in Programming Category

I wanted to get some CPAN authors sample. Not everyone as there are too much (> 8000). So I've created this two on-liners to get the CPAN authors whose module is packaged for Debian:

apt-cache search perl | perl -lane 'next if $_ !~ m/^lib(.+?)-perl\s/; $m=$1; $m=~s/-/::/g; print $m;' > /tmp/deb-perl.txt

zcat ~/.cpan/sources/modules/02packages.details.txt.gz | perl -MIO::Any -lae 'my %x; BEGIN { %x=map { $_ => 1 } split "\n", IO::Any->slurp("/tmp/deb-perl.txt") }; while (<>) { @F=split /\s+/; $m = lc $F[0]; if ($x{$m}) { (undef,undef,$a)=split "/", $F[2]; print $a; }; }' | sort | uniq | xargs echo

And here is the result (842 out of 8270 total):

Here are some variants that I've seen so far.

1. Careful people that are afraid to spoil the system use:

   • /usr/local
   • /var/local
   • /opt

2. Crazy people have always an original place to hide files in:

   • /usr/local64
   • /usr/local/64
   • /usr/local/local
   • /shared
   • /corp
   • /data
   • ...

3. Linux distributions put files according to the Filesystem Hierarchy Standard.

Some years ago I belonged to the first group and I was putting everything into /usr/local to be sure that there is just my stuff. Today I belong to the second one... I use /data for my laptop. Which is not so great idea, but it is my laptop and no one ever will have to (won't even be able) to touch it, so it is my mess. Some of the other ones like /corp, /shared and /usr/local64 I have to use at $work, because it is ops decision or a historical reason (sniff, sniff).

I hope one day I'll further evolve to work according to the standards. Tiding-up my mess would be the easy part of the journey...

Some people say that specifications are useless. That they never reflect the reality, that by the time of being done they are out-dated and people should just rush out, start coding and start working. I found this nice quote:

That was my missing piece to the argumentation. May be the specs at the end are "not so accurate", but at the time of writing them, the idea has to be exercised, questioned, the missing gaps filled in, all details understood and the goal clearly defined.

Joel shows that StackOverflow is (||was?) running on 2 servers (+1 backup) using C# and SQL Server. Impressive :-) seek to 24:56 to see the full performance+tech table.

There is also a Perl+Perl6 mentioned in this talk, seek to 38:00 to hear the #1 thing you should never do...

This was an old idea and I finally found enough toits to finish it. Basically besides normal key words searching, one can use a tag cloud to help find alternatives. Here are some examples:

• +Perl tips
• just search for it
• match algebra +solving
• Wien Wochenende -buchen [de]

By clicking on any of the links in the cloud the keyword/tag is added to the search string. On the top there are "+" and "-" that can be selected before selecting a tag. The selected "+" or "-" will be added in front of the keyword to force inclusion of exclusion of a keyword in the search result documents.

Only time and some usage will tell if it will be useful or not. Let's see.

@@ -1,25 +1,25 @@
-diff -Naur a/DhMakePerl.pm b/DhMakePerl.pm
---- a/DhMakePerl.pm	2010-02-15 17:28:42.000000000 +0100
-+++ b/DhMakePerl.pm	2010-02-15 17:17:55.000000000 +0100
+diff -Naur DhMakePerl.orig/DhMakePerl.pm DhMakePerl/DhMakePerl.pm
+--- DhMakePerl.orig/DhMakePerl.pm	2010-02-19 13:36:58.000000000 +0100
++++ DhMakePerl/DhMakePerl.pm	2010-02-22 18:40:12.000000000 +0100
 @@ -65,6 +65,8 @@
  use WWW::Mechanize ();
  use YAML           ();
  use version qw( qv );
 +use Debian::Apt::PM;
 +our $aptpm = Debian::Apt::PM->new();
  
  # TODO:
  # * get more info from the package (maybe using CPAN methods)
-@@ -1132,8 +1134,12 @@
+@@ -1131,9 +1133,11 @@
+             $dep = Debian::Dependency->new( 'perl',
                  $self->nice_perl_ver( $dep_hash->{$module} ) );
          }
-         elsif ($apt_contents) {
+-        elsif ($apt_contents) {
 -            $dep = $apt_contents->find_perl_module_package( $module,
 -                $dep_hash->{$module} );
-+            #$dep = $apt_contents->find_perl_module_package( $module,
-+            #    $dep_hash->{$module} );
++        else {
 +            my $info = $aptpm->find($module, $dep_hash->{$module});
 +            if ($info and $info->{'min'}) {
 +                $dep = Debian::Dependency->new( $info->{'min'}->{'package'}, $info->{'min'}->{'version'} );
 +            }
          }

This is really hard to read and understand...

Thanks to Yuval Kogman for pointing out this great talk - Systems that Never Stop (and Erlang).

Does anyone knows of a Perl MVC implementation that is based on some event loop? Having non-blocking IO (filesystem/database) in web request handling would be nice to have. That will enable to have just one process per CPU. The IO is the only reason why "one process is NOT enough for every CPU"

Redis - A persistent key-value database with built-in net interface written in ANSI-C for Posix systems. ... see all the commands supported by Redis to get the first feeling

Looks interesting.