From: Lucio De Re <lucio.dere@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 announcements on twitter
Date: Fri, 4 Dec 2020 11:37:05 +0200 [thread overview]
Message-ID: <CAJQ9t7iXVv1b3U7zWhjgV-9Lxt2pqgQS7OAQ2mL3AVmnVWe3kw@mail.gmail.com> (raw)
In-Reply-To: <DD1D5D63-9498-4B78-8AA3-9C6133180373@iitbombay.org>
On 12/3/20, Bakul Shah <bakul@iitbombay.org> wrote:
>
> Finally, I very much doubt he would have liked C!
>
I had an electrical engineering friend, back at university, who used
array subscripts in C because he couldn't get his head around
pointers. Like me, his migration was from Pascal to C.
I would prefer a Modula-2 derived language for code I need to share
with others (that's about all code, in my tradition), but Go is a good
alternative, although I'm not missing it right now, having decided to
punish my colleagues by using their own choice: PHP.
I'd like to find a community that discusses the pros and cons of
programming notations in an objective fashion, rather than the more
common approach to solve some immediate problem with time to market as
the only actual target criterion.
I guess that is like Science Fiction, it keeps slipping into Fantasy.
A revised version of "A Discipline of Programming" could provide a
pretty sound foundation for that kind of discussion, in my opinion. Go
seems to be taking steroids, at the moment, and I have no preference
past it. It's a shame, because a lot of great design was spent on Go.
I don't think anything really valuable was rejected, but a lot was
included that opened far too many doors, in my opinion, of course.
Lucio.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T3fd028fcf2eeb24c-Mc2558e37824facff420258c8
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2020-12-04 9:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 21:36 Skip Tavakkolian
2020-11-13 3:50 ` Lucio De Re
2020-11-13 3:55 ` Don A. Bailey
2020-11-13 3:57 ` Calvin Morrison
2020-11-13 6:31 ` sirjofri+ml-9fans
2020-11-16 0:03 ` [9fans] " cigar562hfsp952fans
2020-11-13 18:45 ` [9fans] " Kim Shrier
2020-11-13 19:05 ` Skip Tavakkolian
2020-11-13 19:09 ` Skip Tavakkolian
2020-11-13 23:23 ` Pouya Tafti
2020-11-16 0:09 ` [9fans] " cigar562hfsp952fans
2020-12-03 3:09 ` cigar562hfsp952fans
2020-12-03 4:01 ` Lucio De Re
2020-12-03 7:25 ` Mart Zirnask
2020-12-03 8:50 ` Lucio De Re
2020-12-03 9:28 ` [9fans] " Bakul Shah
2020-12-04 9:37 ` Lucio De Re [this message]
2020-12-04 13:20 ` hiro
2020-12-05 9:12 ` Lucio De Re
2020-12-05 22:25 ` [9fans] " cigar562hfsp952fans
2020-12-06 3:56 ` Lucio De Re
2020-12-07 4:45 ` Devon H. O'Dell
2020-12-06 19:52 ` Ethan Gardener
2020-12-07 4:28 ` Lucio De Re
2020-11-18 2:34 ` [9fans] " ori
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=CAJQ9t7iXVv1b3U7zWhjgV-9Lxt2pqgQS7OAQ2mL3AVmnVWe3kw@mail.gmail.com \
--to=lucio.dere@gmail.com \
--cc=9fans@9fans.net \
/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).