public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin components.
Date: Thu, 28 Jul 2011 13:21:06 +0200	[thread overview]
Message-ID: <1311852066.2306.4.camel@Desktop666> (raw)
In-Reply-To: <4E30F2DA.6030403@speakeasy.net>

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

On Thu, 2011-07-28 at 01:25 -0400, Alan Grimes wrote:
> I am working on the peer and the wallet boxes in this diagram. I want to 
> implement my own version because the existing code is completely 
> untrustworthy, it is totally slap-dash and almost completely uncommented.
Yay, yet another person who wants to write their own client from scratch
who will get the net code done, work a bit on wallet code and move on to
something more exciting.  Seriously, at this point it seems everyone and
their mother are writing their own, or planning to write their own,
client.
Bitcoin's code actually can be fairly well segmented into the necessary
pieces (CWallet was the first big chunk, more are coming) and comments
are being added as a part of that effort.
The current code is much, much more trustworthy than anything someone
new will start to code, even if they have 20 lines of comments for each
line of code.  If you want to help the project, please dont write yet
another new client library, just look for an existing one you can help
with, or help with the original client.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2011-07-28 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28  5:25 [Bitcoin-development] Bitcoin components Alan Grimes
2011-07-28  5:56 ` Luke-Jr
2011-07-28 11:21 ` Matt Corallo [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=1311852066.2306.4.camel@Desktop666 \
    --to=bitcoin-list@bluematt.me \
    --cc=bitcoin-development@lists.sourceforge.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