From: DervishD <zsh@dervishd.net>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: Stuff to do
Date: Fri, 29 Sep 2006 10:05:24 +0200 [thread overview]
Message-ID: <20060929080524.GE13837@DervishD> (raw)
In-Reply-To: <060928202047.ZM4360@torch.brasslantern.com>
Hi Bart :)
* Bart Schaefer <schaefer@brasslantern.com> dixit:
> On Sep 27, 3:09pm, DervishD wrote:
> } I've read some of the code in zsh and sincerely, I would
> } start it from scratch.
>
> Having worked in the software industry for going on 20 years now, I
> can say with quite some confidence that once a piece of code
> reaches a certain level of complexity, this is almost always the
> wrong approach.
I think that this depends on how messy is the code in the
project. I mean, if the code is so messy (and that doesn't mean
complex) that every time you touch anything you wreck havoc, then
doing something from start is a good idea (IMHO).
I suppose that it's a question of evaluating maintainability
versus the effort of starting from scratch. If a project is barely
maintainable, sometimes it's better to start from scratch, but again
that depends on how complex the design is, of course.
> Zsh passed that level of complexity a very long time ago.
I know, and of course I'm not asking you to start the code from
scratch, I'm just saying that *I* would do it ;)) I have a project
that too passed that level of complexity a time ago, and in fact I
left the project in the hands of the other co-author because I wasn't
motivated enough to continue, and probably rewriting it will be a
complete stupidity, but if I had the time, I swear I'll rewrite it
from scratch. I simply hate maintaining code that tries to resist
every try of being maintained and which contains pieces that nobody
understands XD
With Zsh, I think that I would use a subset of it, as you
suggest, if I would start a "new-Zsh". Rewriting all from the scratch
is probably impossible now, because if you want to create a
bug-compatible version of "new-Zsh" you will probably have to use the
same code, so...
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!
next prev parent reply other threads:[~2006-09-29 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 12:11 Peter Stephenson
2006-09-27 13:09 ` DervishD
2006-09-29 3:20 ` Bart Schaefer
2006-09-29 8:05 ` DervishD [this message]
2006-09-29 16:37 ` Andrey Borzenkov
2006-09-29 17:08 ` Peter Stephenson
2006-09-29 18:08 ` Andrey Borzenkov
2006-09-29 18:08 ` Andrey Borzenkov
2006-10-08 15:38 ` quest for bld_line (was: Re: Stuff to do) Andrey Borzenkov
2006-10-09 12:00 ` Peter Stephenson
2006-10-09 16:28 ` Andrey Borzenkov
2006-10-11 17:54 ` Andrey Borzenkov
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=20060929080524.GE13837@DervishD \
--to=zsh@dervishd.net \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).