unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: Mark H Weaver <mhw@netris.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: Minimal Guile
Date: Tue, 3 Jan 2012 18:09:54 -0800 (PST)	[thread overview]
Message-ID: <1325642994.97968.YahooMailNeo@web37905.mail.mud.yahoo.com> (raw)
In-Reply-To: <87ty4cgt65.fsf@netris.org>

> From: Mark H Weaver <mhw@netris.org>

> What is the advantage of including our own little read-only filesystem,
> when every OS already provides this functionality?  Is it really
> significantly easier to install 3 files than to install 300?
> 
> Admittedly, I can see how it might make a psychological difference.
> Somehow, people get the feeling that a package is huge and bloated when
> it contains a large directory structure, whereas a single file of the
> same size (or even larger) seems significantly less obtrusive.
> 
> However, I'm not sure that this psychological difference is enough to
> justify the reduced flexibility of such an approach.
> 
> Is there an advantage that's not merely psychological?

No, there is no advantage beyond the psychological for any system that
uses the standard Unix-like filesystem hierarchy and has a decent
package manager.

There are some theoretical corner cases where it could be useful.
Don't know if these would ever occur in practice.
- Systems that don't use a Unix-like filesystem heirarchy
- Programs that are distributed in a folder whose root location
  can change
- Programs that use Guile as an extension but want to limit its
  library for some reason.

It is all branding, or marketing, I guess.  And fun, of course. I thought
that, as a hack, it would be fun to try.

Regards,

Mike



  reply	other threads:[~2012-01-04  2:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19 20:35 Minimal Guile Mike Gran
2011-12-19 22:32 ` Noah Lavine
2011-12-21 15:47   ` Andy Wingo
2011-12-21 16:03 ` Mike Gran
2011-12-21 21:05   ` Andy Wingo
2011-12-22  1:07   ` Noah Lavine
2011-12-22  8:13     ` David Kastrup
2011-12-24 15:54   ` Antono Vasiljev
2012-01-03 21:44   ` Ludovic Courtès
2012-01-03 22:53     ` Mike Gran
2012-01-03 23:25       ` Ludovic Courtès
2012-01-03 23:41         ` Mike Gran
2012-01-04  1:20       ` Mark H Weaver
2012-01-04  2:09         ` Mike Gran [this message]
2012-01-04  3:44           ` Mark H Weaver
2012-01-04 18:52             ` Mike Gran
2012-01-05  2:02               ` Mark H Weaver
2012-01-04 19:16             ` Andy Wingo
2012-01-04 20:48               ` Andreas Rottmann

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1325642994.97968.YahooMailNeo@web37905.mail.mud.yahoo.com \
    --to=spk121@yahoo.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mhw@netris.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 read-only IMAP folder(s) and NNTP newsgroup(s).