Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.47 as permitted sender)
	client-ip=209.85.214.47; envelope-from=joel.kaartinen@gmail.com;
	helo=mail-bw0-f47.google.com; 
From: Joel Joonatan Kaartinen <joel.kaartinen@gmail.com>
To: Andy Parkins <andyparkins@gmail.com>
In-Reply-To: <201108110647.35194.andyparkins@gmail.com>
References: <CAJNQ0sudgAnr9hMUMt8grSNTYswunyNnp25Uzw5t17ucxTBoGA@mail.gmail.com>
	<201108102338.21680.andyparkins@gmail.com>
	<CA+8xBpdFH0YtkKPP6hKCf3Q2+2+Lzy0hjjaGYt6y8iBDudJuDw@mail.gmail.com>
	<201108110647.35194.andyparkins@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 11 Aug 2011 14:45:30 +0300
Message-ID: <1313063130.18196.154.camel@mei>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Change to multiple executables?
Precedence: list

On Thu, 2011-08-11 at 06:47 +0100, Andy Parkins wrote:
> Again you're missing my point... you are still shooting ideas down.

And you're only shooting his actions down without indicating clearly
what you think ought to be done instead. What do you want him to say
instead?

> > community also seems rather hard-wired against breaking changes like
> > that, because it implies that we lowly dev peons are daring to mess
> > with the Blessed Satoshi Design that has received extensive study, and
> > 100% communal agreement.
> 
> Well the community had better unhardwire itself or its going to end up with 
> five developers and no more.

No way that will happen. A fork is going to happen sooner rather than
later if this continues. It'd be great if it could be done within this
project and named bitcoin-dev or bitcoin-next or similar.

If this is not done, I wouldn't be surprised with the network splitting
into 2 camps with different protocols but still working on the same
blockchain.

> > If the community changes its mind, and there are strong calls to make
> > a breaking change, we can certainly do that.  Bitcoin is not only open
> > source but very much democratic -- people vote by choosing which
> > client software to use.
> 
> Voting with ones feet should be a last resort.  Wouldn't it be better not to 
> end up with incompatible clients out there?

There's no way to get the majority to vote with their feet to move to an
incompatible client. Not immediately anyway. It can happen gradually
though.

As in: 1) alternative client is published that is compatible but
extended. 2) this client gets the majority share of users/miners 3) they
see this and decide to break compatibility. 4) original bitcoin client
is now incompatible/history.

> > It's negative to weight costs vs. benefits?  That is what I expect any
> > good engineer to do.
> 
> I don't think that's what's happening.  Not once have I seen the "benefits" 
> side of that equation.  What I have seen is plenty of "I can't see a use 
> case for that"; when the key word in that sentence is "I".

What is happening here is that most suggestions you point at have been
discussed about before and so the "early adopter" developers remember
that a decision about that was made already. However, the problem here
lies with the fact that it's difficult to find the previous
conversations.

If there was a section in the wiki for recording past suggestions, there
would be no need to say 'no'. You could instead say "We have discussed
this before, please read..." and give them a link to the page with the
relevant discussion. Of course, this would require actively forwarding
people to the wiki for discussions and having them there. I think this
would be a good idea.

That would leave this list for discussing and coordinating the
implementation of the changes that have been agreed on.

For things that have already been discussed, you could try to find the
previous discussion and add it there. But I expect for some things, new
discussion needs to be had to get it on the wiki.

- Joel