9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] devtrace release time
Date: Thu, 18 Dec 2008 13:32:58 -0500	[thread overview]
Message-ID: <d05abb8c42c2cafa1494be94426c4870@quanstro.net> (raw)
In-Reply-To: <140e7ec30812181006k1d44ccdfke1d748203b4d6e7c@mail.gmail.com>

On Thu Dec 18 13:08:15 EST 2008, sqweek@gmail.com wrote:
>  No no no, this is all release oriented stuff! Just put the code up so
> if someone really interested happens by they can check it out and work
> the details out themselves. What's the disadvantage there?

i think you have to understand that some people do not
approve of hanging their dirty laundry in public.  i think
one has to afford them this space.

>  Of course. But it's silly to entertain the notion that code comes off
> our fingertips perfect and fully formed. It's software: there's bugs,
> there's design flaws, development is incremental. Often it can be
> useful long before it is perfected.
[...]
> > whats worse is if you publish a tar and then somone fixes a load of
> > stuff but in the meantime you are working and your code gets out of sync
> > so you have to merge by hand.
[...]
>  At least this represents a modicum of cooperation. Without the

i have some experience in this.  i've published some
plan 9 early.

the downside is that you no longer have any control.
and thus you can't necessarly get bug fixes published.
there is no law that says, if you accept the original,
you must accept bug fixes and improvements.

so if one cares about the quality of the result, one
believes in one's own abilities, publishing a finished
thing can make a lot of sense.

this isn't what i do, and i pay a price for it.

- erik



  reply	other threads:[~2008-12-18 18:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 19:36 john
2008-12-17 19:50 ` Uriel
2008-12-17 19:55   ` john
2008-12-17 20:08     ` Uriel
2008-12-17 22:07       ` ron minnich
2008-12-17 22:18         ` Eric Van Hensbergen
2008-12-17 23:34         ` Devon H. O'Dell
2008-12-18  3:52         ` lucio
2008-12-18  4:38           ` Uriel
2008-12-18  4:55           ` john
2008-12-18  4:59             ` Nathaniel W Filardo
2008-12-18  5:04               ` john
2008-12-18  5:08                 ` Uriel
2008-12-18  6:10               ` lucio
2008-12-18  8:08           ` sqweek
2008-12-18  8:47             ` lucio
2008-12-18 11:33               ` sqweek
2008-12-18 11:42                 ` lucio
2008-12-18 13:26                   ` erik quanstrom
2008-12-18 16:30                   ` sqweek
2008-12-18 16:54                     ` Steve Simon
2008-12-18 17:02                       ` lucio
2008-12-18 18:06                       ` sqweek
2008-12-18 18:32                         ` erik quanstrom [this message]
2008-12-18 19:06                     ` C H Forsyth
2008-12-18 22:50                       ` sqweek
2008-12-18 23:59                         ` ron minnich
2008-12-18 16:42               ` ron minnich
2008-12-18 16:59                 ` lucio
2008-12-18 16:25             ` ron minnich

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=d05abb8c42c2cafa1494be94426c4870@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).