Computer Old Farts Forum
 help / color / mirror / Atom feed
From: thomas.paulsen at firemail.de (Thomas Paulsen)
Subject: [COFF] Most Popular Programming Languages 1965 - 2019
Date: Fri, 27 Dec 2019 19:24:52 +0100	[thread overview]
Message-ID: <8abbdcabf349359248223c65d511ab1f@firemail.de> (raw)
In-Reply-To: <CAP2nic3bnJHrSOrb8PmWHiNiwy48Nwm1mJN_yWnapjV1_cw8Nw@mail.gmail.com>

> I work in Python for my day job.  Every day I use PyPi, the third-party
> package repository, and every time I do I miss CPAN.  Sure, there was a
> lot of crap in CPAN but the repository itself was well organized.  
I agree. The perl package system is very good. On the other hand the golang 
package system is very good too, and it was even better, when the compiler 
still was written in C;  thus much faster than today's written in go.




  reply	other threads:[~2019-12-27 18:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16  1:33 robert
2019-12-17 22:54 ` paul.allan.palmer
2019-12-17 23:02   ` clemc
2019-12-21 22:22 ` grog
2019-12-22  0:42   ` cym224
2019-12-22 16:51   ` krewat
2019-12-22 21:36     ` dave
2019-12-22 22:05       ` paul.allan.palmer
2019-12-23 17:04       ` krewat
2019-12-23 19:54         ` thomas.paulsen
2019-12-23 21:59           ` krewat
2019-12-23 23:15             ` thomas.paulsen
2019-12-27 16:28               ` athornton
2019-12-27 18:24                 ` thomas.paulsen [this message]
2019-12-27 21:42                   ` tih
2019-12-27 22:13                     ` paul.allan.palmer
2019-12-23 23:03       ` [COFF] Gnu Smalltalk or...? [was: Most Popular Programming Languages 1965 - 2019] rtomek
2019-12-24 17:46         ` bakul
2019-12-25 17:50           ` rtomek
2019-12-22 22:41     ` [COFF] Most Popular Programming Languages 1965 - 2019 grog
2019-12-21 23:32 thomas.paulsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8abbdcabf349359248223c65d511ab1f@firemail.de \
    --to=coff@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).