Computer Old Farts Forum
 help / color / mirror / Atom feed
From: lm at mcvoy.com (Larry McVoy)
Subject: [COFF] What languges would you like to learn?
Date: Tue, 24 Dec 2019 08:35:51 -0800	[thread overview]
Message-ID: <20191224163551.GA3839@mcvoy.com> (raw)
In-Reply-To: <129b28e1-5629-2742-bb04-dfe6161ea3f0@telegraphics.com.au>

On Tue, Dec 24, 2019 at 11:28:12AM -0500, Toby Thain wrote:
> On 2019-12-23 6:27 p.m., Nemo Nusquam wrote:
> > A recent thread makes me wonder which languages would people like to
> > learn??? (I confess to trying, as Dave does, but time prevents anything
> > more that learing syntax and writing toy programmes.?? One must write
> > something substantial -- not synonomous with large -- to really learn a
> > language.)
> > 
> > Erlang, Smalltalk, Prolog, Haskell, and Scheme come to mind...
> 
> You have GREAT taste, and that covers the major paradigms.

As a systems guy who likes to get all the perf he can out of the machine,
those are not what I'd reach for 1st, 2nd, or 3rd.  I still like C, it's
what I reach for first.  Go might be second.

For scripting I designed http://little-lang.org which looks a lot like
interpreted C with a bunch of neat extensions (ever wanted strings in
your switch() statement?  How about regexps?).  I

The listed languages are what a very small set of programmers passionately
love but they never go anywhere because the rank and file programmers don't
get it.  I can think of lots of examples where some smart dude pushed 
lisp in a company and it either never went anywhere or it died when the
dude left.

There is a lot to be said for programming in the most simple way possible,
we had a saying at my company "Write code so it is the most readable.
Because 6 months from now you'll not remember it, it will be like reading
someone else's code".

Code is write once, read many.  Optimize for that.


  reply	other threads:[~2019-12-24 16:35 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23 23:27 cym224
2019-12-24  9:54 ` thomas.paulsen
2019-12-24 16:28 ` toby
2019-12-24 16:35   ` lm [this message]
2019-12-24 17:50     ` 
2019-12-24 18:04       ` lm
2019-12-25  3:34     ` dave
2019-12-25 16:02     ` cym224
2019-12-25 17:05     ` thomas.paulsen
2019-12-24 20:27 ` dave
2019-12-25 17:31 ` rtomek
2019-12-25 19:13   ` athornton
2019-12-26  0:23     ` me
2019-12-26  1:54       ` wobblygong
2019-12-26  3:44         ` dave
2019-12-26  4:00           ` lm
2019-12-26  5:43             ` wobblygong
2019-12-26 11:49               ` tih
2019-12-26 15:33                 ` lm
2019-12-26 16:34                 ` thomas.paulsen
2019-12-26 16:53                   ` lm
2019-12-27  3:00                 ` dave
2019-12-27  7:02                   ` thomas.paulsen
2019-12-26 17:57               ` bakul
2019-12-26 21:28                 ` davida
2019-12-26 21:37                   ` lm
2019-12-26 21:57                     ` sauer
2019-12-26 22:13                     ` 
2019-12-27  3:41                     ` bakul
2019-12-27  4:00                       ` lm
2019-12-27  4:28                         ` bakul
2019-12-26 22:16                   ` imp
2019-12-27  3:41                   ` bakul
2019-12-26 15:43         ` dfawcus+lists-coff
2019-12-27 17:46   ` cym224
2019-12-27 21:33     ` tih

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=20191224163551.GA3839@mcvoy.com \
    --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).