9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] extensions of "interest"
Date: Thu,  9 Apr 2009 22:05:58 -0700	[thread overview]
Message-ID: <20090410050558.AEF725B12@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 09 Apr 2009 17:10:47 MDT." <14ec7b180904091610y3fd8abdao1ebca4d19d77246a@mail.gmail.com>

On Thu, 09 Apr 2009 17:10:47 MDT andrey mirtchovski <mirtchovski@gmail.com>  wrote:
> > Unfortunately we don't have exact analogs in s/w.  We can
> > only simplicate; we can't add lightness!
>
> but somehow we can add "weight". can't we? bash is perceivably
> "heavier" than rc, xml perceivably "heavier" than 9p... statlite()
> perceivably "heavier" than stat() :)

Yes of course.  But that is because they use a more
complicated design that results in use of more code.

What I meant is in a physical assembly you can carefully
hollow out a solid part or use a lighter material to get a
lighter part without changing its structural properties
(much) and no other parts or couplings have to be changed.

In a program one can use hand code asembly or inline code
instead of calling a function, or call a function instead of
RPC to a separate process and so on but in each case there is
a tighter coupling that reduces flexibility.

Design done by wizards have simpler and fewer parts -- they
are simply much better at design. They "simplicate".

But granted, the analogy is rather weak :-)



  reply	other threads:[~2009-04-10  5:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 17:17 ron minnich
2009-04-09 17:25 ` erik quanstrom
2009-04-09 17:34   ` J.R. Mauro
2009-04-09 17:40     ` erik quanstrom
2009-04-09 17:43     ` andrey mirtchovski
2009-04-09 17:48       ` erik quanstrom
2009-04-09 17:58         ` J.R. Mauro
2009-04-09 17:59         ` andrey mirtchovski
2009-04-09 18:06           ` Anthony Sorace
2009-04-09 21:25           ` Steve Simon
2009-04-09 21:30             ` andrey mirtchovski
2009-04-09 21:31               ` andrey mirtchovski
2009-04-09 22:30                 ` Skip Tavakkolian
2009-04-09 22:45                   ` andrey mirtchovski
2009-04-10 12:40                   ` John P. Cummings
2009-04-09 23:06                 ` Bakul Shah
2009-04-09 23:10                   ` erik quanstrom
2009-04-10  5:16                     ` lucio
2009-04-11 23:34                       ` Russ Cox
2009-04-12  2:42                         ` Anthony Sorace
2009-04-12  4:53                           ` lucio
2009-04-14  0:03                           ` dave.l
2009-04-09 23:10                   ` andrey mirtchovski
2009-04-10  5:05                     ` Bakul Shah [this message]
2009-04-09 23:20                   ` Robert Raschke
2009-04-09 19:05       ` maht
2009-04-09 19:16         ` J.R. Mauro
2009-04-09 19:22           ` erik quanstrom
2009-04-09 19:40             ` J.R. Mauro
2009-04-09 19:43             ` Mechiel Lukkien
2009-04-10  1:35       ` LiteStar numnums

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=20090410050558.AEF725B12@mail.bitblocks.com \
    --to=bakul+plan9@bitblocks.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).