Computer Old Farts Forum
 help / color / mirror / Atom feed
From: tih at hamartun.priv.no (Tom Ivar Helbekkmo)
Subject: [COFF] What languges would you like to learn?
Date: Thu, 26 Dec 2019 12:49:20 +0100	[thread overview]
Message-ID: <m236d7xq67.fsf@thuvia.hamartun.priv.no> (raw)
In-Reply-To: <CACNPpeYjchtOF_caAwui2AhAdguHHYJepVVmG4DFnF+wx-Nk4A@mail.gmail.com> (Wesley Parish's message of "Thu, 26 Dec 2019 18:43:17 +1300")

Wesley Parish <wobblygong at gmail.com> wrote:

> It took immersion into Java before I finally got the hang of object
> orientation, and Java's still a lot smaller than C++.

This quote may be relevant to that:

"I made up the term 'object-oriented', and I can tell you I didn't
have C++ in mind!"  --Alan Kay to Bjarne Stroustrup at OOPSLA 1997.

...and here's GLS, answering critical comments about Java:

"We were not out to win over the Lisp programmers; we were after the
C++ programmers.  We managed to drag a lot of them about halfway to
Lisp.  Aren't you happy?"    --Guy L. Steele on the creation of Java

Larry McVoy <lm at mcvoy.com> wrote:

> C++ seems to encourage complexity and I hate complexity.

This reminds me of something Erik Naggum said (about another language,
and in harsher words (as was his wont), but the underlying point about
the language affecting how problems are solved is the same):

"It's not that perl programmers are idiots, it's that the language rewards
idiotic behavior in a way that no other language or tool has ever done."

-tih
-- 
Most people who graduate with CS degrees don't understand the significance
of Lisp.  Lisp is the most important idea in computer science.  --Alan Kay


  reply	other threads:[~2019-12-26 11:49 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
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 [this message]
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=m236d7xq67.fsf@thuvia.hamartun.priv.no \
    --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).