9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] tcl, 9p
Date: Mon, 10 Oct 2011 17:16:44 -0400	[thread overview]
Message-ID: <c8df5a0ba932ebd53bb37c5e42f106c0@chula.quanstro.net> (raw)
In-Reply-To: <CAFUsep0WRifUREf=BuX2hMT85g46pObH-3Q6XFcf82ONOGTeEw@mail.gmail.c>

On Mon Oct 10 09:52:36 EDT 2011, ph.softnet@gmail.com wrote:
> It's not necessary that you're feeding a troll, in my opinion.
> I actually agree with the idea that C is enough.
> I don't understand why you need garbage collection ... why do you need
> to have garbage in the first place?
> Just because time goes by does not mean everything should keep on
> changing you know.
> People have to understand that certain technologies can just stay as
> they are, if they work well.

"need" is such a funny word.  we don't need keyboards, we can just use
toggles.  there have been a few other trivial improvments in the day-to-day
lives of programmers like bitmap displays, which real computer scientists can ignore.

so as time goes on, it's easy for programmers to get a whiggish view of the world.
but you're equally correct, that the mere passage of time between x and y is not
an argument that either is better.

so we're left only to argue this one on the merits of garbage collection.  :-)
now that i think of it, garbage collection was invented more than a decade
before c.  so the preceeding two paragraphs have been argued in the moot
court.  in any event, i think one can consider manual memory management
to often be akin to manually managing registerization.  there is a good chance
that in most cases that an automatic and systematic process can do a better
job than an ad hoc one.

yet, i program in c most of the time.  i don't know of many operating
systems written in a automaticly gc'd language.

- erik



  parent reply	other threads:[~2011-10-10 21:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09  0:02 L N
2011-10-09  2:31 ` Russ Cox
2011-10-09  3:20   ` L N
2011-10-09  3:30     ` Venkatesh Srinivas
2011-10-10  9:05   ` Balwinder S Dheeman
2011-10-10 13:33     ` Paul Lalonde
2011-10-10 13:51       ` simon softnet
2011-10-10 16:57         ` Wes Kussmaul
2011-10-11  7:50           ` hiro
2011-10-11  8:34             ` L N
     [not found]       ` <CAFUsep0WRifUREf=BuX2hMT85g46pObH-3Q6XFcf82ONOGTeEw@mail.gmail.c>
2011-10-10 21:16         ` erik quanstrom [this message]
2011-10-26 16:45       ` Balwinder S Dheeman
2011-10-09  5:21 ` ron minnich
2011-10-09  6:15   ` pmarin
     [not found]   ` <CAOe8CcYL4J5Uu4MSwpT8bO=4LC7omJ84FDkRy=ZXzq8wNH5iWg@mail.gmail.c>
2011-10-09 13:12     ` erik quanstrom
2011-10-09 17:24       ` simon softnet
2011-10-09 23:05         ` Nick LaForge
2011-10-27  7:46 ` Axel Belinfante
2011-10-10 20:55 Winston Kodogo

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=c8df5a0ba932ebd53bb37c5e42f106c0@chula.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).