9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: George Michaelson <ggm@apnic.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Plan9 Programming languages ! -- The Future !
Date: Fri, 14 Dec 2001 03:51:36 +1000	[thread overview]
Message-ID: <27962.1008265896@apnic.net> (raw)
In-Reply-To: Your message of "Thu, 13 Dec 2001 17:26:24 +0000." <9vane1$g9s$1@ctb-nnrp2.saix.net>


> According to my opinion - The success, future etc etc. of any operating
> system (Plan9 in this case) depends on its ability to be programmed by all
> possible programmers (in more languages has possible etc) No Software !! -
> No Users etc !!! :-}

success is very subjective. the Apollo-11 OS was a fantastic success
given the engineering constraints but the UI was maybe a bit tortuous.

language plethora is a good thing in research space and usually a bad
thing in deployment. my experience is that it massively increases the
opportunity for bad behaviour. GC/VM models, IPC, program-system boundarie
turn out not to be completely abstract but reflect the language of
implementation (is that unfair?)

My brother is a lamda calculus expert. I would find it very hard to
survive in his domain, but I also suspect good programmers would achieve
very very good things if that was the 'one true way'

The Pascal discussion reminded me of my first feelings on the apparent
convergeance of the algol-60 and fortran i/o binding mechanisms. How wierd!
two languages so different yet one apparent method to say how to connect
to a punch or a reader. Then to get Pascal, and have to come to terms with
its bindings..

I suspect any language with i/o or IPC a first-class concept in the language
and not buried under methods or procedure call interfaces would blow my
lobes. rendesvous between asynchronous real-world events, or the emulation
of parallelism in a serial instruction machine and how that exposes to
the apparently discrete programs is a wonderful opportunity for language
designers to play the deity and show their view of 'how it is done wrong'

I hope P9 remains a small-set-of-ported-languages space. I think it will be
better for it. One from the lisp family, one from the interpreter space,
one from the C gang, one for old timers. one shell/rc to bind them. one
namespace scheme to find them.

cheers
	-George


  reply	other threads:[~2001-12-13 17:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 17:13 [9fans] Plan9 Programming languages ! D De Villiers
2001-12-06 18:17 ` Matt Senecal
2001-12-06 19:02 ` William S .
2001-12-10 10:02   ` D De Villiers
2001-12-07  9:36 ` [9fans] " Douglas A. Gwyn
2001-12-07 11:51   ` Boyd Roberts
2001-12-10 10:01 ` [9fans] Re: Plan9 Programming languages ! -- PASCAL? D De Villiers
2001-12-11 10:07   ` Douglas A. Gwyn
2001-12-12  9:48     ` Thomas Bushnell, BSG
2001-12-13 10:26       ` Douglas A. Gwyn
2001-12-13 12:04         ` Wladimir Mutel
2001-12-14 10:15           ` Douglas A. Gwyn
2001-12-14 10:14         ` Thomas Bushnell, BSG
2001-12-14 17:04           ` Douglas A. Gwyn
2001-12-17 10:15             ` Thomas Bushnell, BSG
2001-12-14 17:37         ` D De Villiers
2001-12-17 10:14         ` Daniel Warmuth
2001-12-18 17:27           ` D De Villiers
2001-12-18 19:35             ` Matt
2001-12-13 17:26       ` [9fans] Re: Plan9 Programming languages ! -- The Future ! D De Villiers
2001-12-13 17:51         ` George Michaelson [this message]
2001-12-12 17:12     ` [9fans] Re: Plan9 Programming languages ! -- PASCAL? D De Villiers
2001-12-14 10:15       ` north_
2001-12-12 17:21   ` [9fans] Re: Plan9 Programming languages -- Anyother ? D De Villiers
2002-01-02 10:04   ` [9fans] Re: Plan9 Programming languages ! -- PASCAL? kim kubik
2002-01-02 11:12     ` mark powers
2002-01-02 11:22     ` Jon Snader
2002-01-02 11:31     ` Ralph Corderoy

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=27962.1008265896@apnic.net \
    --to=ggm@apnic.net \
    --cc=9fans@cse.psu.edu \
    /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).