From: linas@linas.org (Linas Vepstas)
Cc: guile-lib-dev@gnu.org, Guile Users <guile-user@gnu.org>
Subject: Re: guile-lib things
Date: Sun, 27 Jun 2004 16:43:07 -0500 [thread overview]
Message-ID: <20040627214307.GT3998@backlot.linas.org> (raw)
In-Reply-To: <87isdfpjzy.fsf@trouble.defaultvalue.org>
On Fri, Jun 25, 2004 at 01:31:29PM -0500, Rob Browning was heard to remark:
> Andy Wingo <wingo@pobox.com> writes:
>
> > [0] At one point, I wanted strictly taxonomic names for the
> > modules. I was wrong: code doesn't behave taxonomically, it behaves
> > in a certain quirky way depending on who wrote it / what package it
> > comes from. So while you might classify _packages_ a certain way,
> > the code often deserves to be classified under the package name
> > itself. I'm thinking of (sxml htmlprag) here.
>
> That said, I tend to prefer flatter namespaces for modules when
> there's a choice. For example, modules like (text regexp pcre), (db
> relational sql postgresql), or even (graphics opengl) seem
> unnecessary and even potentially confusing to me.
Yes! Deep taxonomies also hinder authors who are working on
new stuff, which tends to cross boundaries: if it could be easily
classified, it would be a whole lot more boring, and maybe not
worth doing .... For example, suppose you had to classify a blog
tool, say 5 years ago. What category would you have put it then?
Is slashdot a blog or a news agregator? Who knows?
--linas
--
pub 1024D/01045933 2001-02-01 Linas Vepstas (Labas!) <linas@linas.org>
PGP Key fingerprint = 8305 2521 6000 0B5E 8984 3F54 64A9 9A82 0104 5933
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-06-27 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 18:03 guile-lib things Andy Wingo
2004-06-25 11:48 ` Andy Wingo
2004-06-25 18:31 ` Rob Browning
2004-06-27 21:43 ` Linas Vepstas [this message]
2004-06-29 17:43 ` Andy Wingo
2004-06-30 22:20 ` Rob Browning
2004-07-08 19:01 ` Andy Wingo
2004-07-03 16:48 ` Thien-Thi Nguyen
2004-07-10 4:44 ` Linas Vepstas
2004-06-27 1:22 ` ASDF for guile (Was Re: guile-lib things) Chris Hall
2004-06-28 13:33 ` Matthew Trout
2004-06-28 13:48 ` Andy Wingo
2004-07-01 21:42 ` guile-lib things Neil Jerram
2004-07-08 19:09 ` Andy Wingo
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=20040627214307.GT3998@backlot.linas.org \
--to=linas@linas.org \
--cc=guile-lib-dev@gnu.org \
--cc=guile-user@gnu.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).