From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QgCrb-0008MQ-7D for bitcoin-development@lists.sourceforge.net; Mon, 11 Jul 2011 09:33:15 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.220.175 as permitted sender) client-ip=209.85.220.175; envelope-from=mh.in.england@gmail.com; helo=mail-vx0-f175.google.com; Received: from mail-vx0-f175.google.com ([209.85.220.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1QgCrV-00065y-Le for bitcoin-development@lists.sourceforge.net; Mon, 11 Jul 2011 09:33:15 +0000 Received: by vxa37 with SMTP id 37so3764071vxa.34 for ; Mon, 11 Jul 2011 02:33:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.68.75 with SMTP id u11mr1956010vdt.334.1310376784130; Mon, 11 Jul 2011 02:33:04 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.52.164.225 with HTTP; Mon, 11 Jul 2011 02:33:04 -0700 (PDT) In-Reply-To: <97305540.4426247.1310337435268.JavaMail.fmail@mwmweb052> References: <97305540.4426247.1310337435268.JavaMail.fmail@mwmweb052> Date: Mon, 11 Jul 2011 11:33:04 +0200 X-Google-Sender-Auth: 9BdROXknMGbRR6Y66RWHQMoLWc8 Message-ID: From: Mike Hearn To: Michael Offel Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1QgCrV-00065y-Le Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] overall bitcoin client code quality X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2011 09:33:15 -0000 > My overall suggestion is to begin a complete rewrite, inspired by the old > code rather than moving a lot of "known to be somehow functional" around. This essay is old but still relevant, I think: http://www.joelonsoftware.com/articles/fog0000000069.html Despite that, there are efforts to write a fresh implementation. For example, BitCoinJ: http://code.google.com/p/bitcoinj/ It is not a complete implementation. It's targeting the "simplified payment verification" mode as a first base, and is mostly intended for mobile phones today as that's a niche the current codebase can't meet. In the (very) long run, it may evolve into a full node. > Hopefully I did not hurt someone's feelings. The code was written by Satoshi who is long gone, and I doubt he would care much for this type of list anyway. He was a do-er rather than a talker.