Dwindling CPAN Releases

Post by cure » Fri, Aug 02, 2019, 1:11 PM UTC

perigrin wrote: post #131

cure wrote: post #110

Earlier quoted context omitted.

The other place where this principle is completely ignored is when it comes to Python packaging, which is a complete and utter disaster. There are many different ways to package Python, none of them are feature complete, and the result is an absolute maintenance nightmare for those of us who have to maintain tools that have Python dependencies. Perl got packaging right, there's one way to do it, and it just works!

There isn't one way to do it in Perl (EUMM, Module::Build, Module::Build::Tiny, Module::Install etc), we just tried to make sure that they all interoperated cleanly. And we have things like the Toolchain Summit to make an emphasis on that.

Post by daotoad » Fri, Aug 02, 2019, 3:21 PM UTC

hobojones wrote: post #117

I work on a large, legacy codebase (the oldest modules date from the mid-nineties) that's slowly being rewritten from Perl into Python. A handful of developers have been involved with the project from the beginning. Looking at the long term contributors, readable or un-readable code seems to be more about the person than the language. Unsurprisingly, the person who produced the most unreadable, unmaintainable code is…

Post by gkfasdfasdf » Fri, Aug 02, 2019, 4:48 PM UTC

markoman wrote: post #164

gkfasdfasdf wrote: post #97

I still use perl for handy one liners on the command line. E.g. I had a 1 GB log file where I wanted to generate a histogram of the intervals between certain log messages. I used a perl one-liner to extract the timestamp via regex (regexs are perl's bread and butter), calculate the diff between the previous timestamp (easy because of auto string => double conversion), use the diff value as a key in a hash of counters…

I'm an occasional perler myself and I bet that others or myself would find that code you mention to be useful, at least for the black book of snippets. Would you mind pasting?

  rg ''  | \
  perl -MData::Dumper -n -e '
  m/\d{2}:\d{2}:([\d.]+)/;
  if ($last) {
    $diff = $1 - $last;
    print "$diff\n";
    $hist{$diff} += 1;
  }
  $last = $1;
  END {
    $Data::Dumper::Sortkeys = true;
    print Dumper(\%hist);
  }
  '

Post by abacadaba » Fri, Aug 02, 2019, 8:53 PM UTC

simcop2387 wrote: post #121

VVertigo wrote: post #73

Earlier quoted context omitted.

Didn't perl always have multi-dimensional arrays? Just the syntax sugar for them is more recent.

Not quite, references were introduced in perl 5, in perl 4 and earlier had a different method that wasn't quite multi-dimensional arrays but tried to behave that way. $hash{1,2,3} = 10; This actually ends up doing the following $hash{join($;, 1, 2, 3)} = 10; It builds up a single key from the list using the special variable $; as a separator to the elements. With perl 5 you gained the ability to make references which…

Post by anomalizer » Wed, Aug 07, 2019, 5:28 AM UTC

cheeze wrote: post #152

roryrjb wrote: post #95

There's so much negativity in this thread. I think that a big part of Perl's decline is exactly because of people's attitudes. I don't actually write any Perl now, but to me it's a beautiful language, I always enjoy working in it. You can abuse it in the wrong way like every other language. If I was to suggest using it in the day job there would be uproar probably. But just because I like Perl doesn't mean I want to…

Prel is great and has an important role, even today. That being said, I'm a professional dev and we own a decent amount of perl. That codebase is by far the most difficult to work in out of anything we own. New hires have trouble with it (nobody learns perl these days). Lots of it is next to unreadable. I agree that like any other language, perl can be written well and can be written poorly. That being said, perl mak…