From: Jan Larres <jan@majutsushi.net>
To: zsh-workers@zsh.org
Subject: Re: PATCH: overwrite mode shouldn't replace newlines
Date: Mon, 01 Dec 2014 10:42:34 +1300 [thread overview]
Message-ID: <m5g30c$rj5$1@ger.gmane.org> (raw)
In-Reply-To: <547B7649.4020509@eastlink.ca>
On 01/12/14 08:55, Ray Andrews wrote:
> On 11/30/2014 11:24 AM, Bart Schaefer wrote:
>> Like most open-source projects dating from the late 80s, zsh relied on
>> users to test and report bugs. There has never been enough volunteer
>> manpower for a dedicated all-code-paths testing regimen, so a bug that
>> a real user never encounters will only rarely be fixed.
> That is demonstrably the case. But as a guy who's done some testing in a project
> I can't help but notice that trying overstrike mode would be one of the first
> things I'd have done. It's another cultural adjustment for me.
Open Source projects, unless they're run by a company, rarely have
dedicated testers whose only job it is to look for bugs. Sometimes
people decide to spend some time on that due to a sense of duty, but
generally it makes more sense to spend time on areas that actually
benefit the most people, or that interest the contributor personally,
instead of trying to find every last bug (which is impossible anyway).
The fact that this bug apparently wasn't discovered until now or at
least not deemed important enough by users to report it shows that not
that many people would have benefited from a comprehensive testing
approach here. Of course doing more testing is generally a good thing,
but there is also a cost/benefit factor to consider, especially for
volunteer-run projects.
-Jan
prev parent reply other threads:[~2014-11-30 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 0:04 Oliver Kiddle
2014-11-30 1:23 ` Ray Andrews
2014-11-30 19:24 ` Bart Schaefer
2014-11-30 19:55 ` Ray Andrews
2014-11-30 21:42 ` Jan Larres [this message]
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='m5g30c$rj5$1@ger.gmane.org' \
--to=jan@majutsushi.net \
--cc=zsh-workers@zsh.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.
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).