From: "cr88192 sydney" <cr88192@hotmail.com>
Subject: Re: top-down design + nevermind
Date: Tue, 09 Apr 2002 02:55:56 +0000 [thread overview]
Message-ID: <F36mZ2UN3YZ6w1iE3T500008530@hotmail.com> (raw)
>
>this is related to recent guile-snarf weirdness but could be said to
>apply generally to ends such as setting guile's direction. top-down
>design values interface elegance more than implementation elegance. the
>implementation does what it needs to support the interface and in return
>for bearing this burden is given the freedom to evolve.
>
>this is obviously in contrast to bottom-up design which i believe can
>get a lot of unfocused work done but often presumes to know the future
>too much in practice, eventually causing re-design, because elegance is
>measured in the implementation and guesses are made about usage.
>
>either style of design is fun. people write books about their own
>personal design philosophies and how it helps you (10min a day). in any
>case, what users perceive determines their happiness w/ the result.
>
>so how to choose the style that fits best for the job?
>
I use both, for my os I use bottom up design and for my compiler I used top
down.
main difference: top down is a lot faster it would seem (a few hours vs.
months), however top down becomes increasingly harder as complexity
increases (at least in my experience).
also top down tends to yeild code which is quite difficult to reuse in
another project (my compiler + my os), and quite difficult to change later
or maintain...
>
>what is guile's direction, btw?
>
I think it is more bottom up...
no one started coding an ide and came up with guile/scm in the process. just
now are ide's starting to form... (as far as I know).
in a whole cs and science in general seem to be a bottom up process, with
occasional "products" that are built in the top down manner...
I support bottom up in general, but would not recommend it if time is a big
issue...
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2002-04-09 2:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 2:55 cr88192 sydney [this message]
[not found] <E16uQmt-0000lA-00@giblet>
2002-04-08 12:47 ` top-down design + nevermind Bill Gribble
2002-04-08 23:08 ` news
2002-04-22 7:34 ` Thien-Thi Nguyen
[not found] ` <1018270049.27252.36.camel@flophouse>
2002-04-21 7:29 ` Thien-Thi Nguyen
2002-04-23 21:16 ` news
2002-04-24 16:59 ` MJ Ray
2002-04-24 19:12 ` Christopher Cramer
[not found] ` <crayc@pyro.net>
2002-04-24 21:53 ` MJ Ray
2002-04-24 19:44 ` news
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 4:29 Thien-Thi Nguyen
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=F36mZ2UN3YZ6w1iE3T500008530@hotmail.com \
--to=cr88192@hotmail.com \
/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).