From: Peter Todd <pete@petertodd•org>
To: Achow101 <achow101-lists@achow101•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Cc: Ahmer Regos <ahmerregos@gmail•com>
Subject: Re: [bitcoin-dev] Improving Pre and Post Merging Abilities With Rewriting Core In Python
Date: Fri, 26 Apr 2019 23:32:27 -0400 [thread overview]
Message-ID: <20190427033227.g5t3p7meztdc6tr4@petertodd.org> (raw)
In-Reply-To: <V0VmX7UXCj3jIAzs4ChvyjabCLbjKvyOCURUOoR9q1y0xOcYO8Dl7aMYzIE0qoROqkVZQ4EpxCgD6UA2pBhWM_dfAwvYK7GVZcbs8EoSmW4=@achow101.com>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Tue, Apr 23, 2019 at 03:23:27PM +0000, Achow101 via bitcoin-dev wrote:
> Feel free to re-implement Bitcoin Core in Python. It's open source software and you can do whatever you want.
>
> However Bitcoin Core is not going move to Python and rewrite everything in Python. Besides the fact that Python is far less efficient than C/C++, rewriting Bitcoin Core in any other language would be a huge undertaking and introduce many bugs for almost no benefit whatsoever. Bitcoin Core won't be changing languages for the entire codebase, but you are welcome to port it to Python yourself.
Speaking as maintainer of the Python library python-bitcoinlib, I don't think
using Python for security critical codebases is a good idea. It's just too easy
to make mistakes; I wouldn't recommend new projects use python-bitcoinlib.
Currently I'm doing 100% of my new projects on Rust. That's not to say Rust is
the only language usable for this kind of work. But it fits my style of
programming well and the type system - esp good handling of immutability -
appears to offer significant benefits.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-27 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 8:16 Ahmer Regos
2019-04-23 15:23 ` Achow101
2019-04-27 3:32 ` Peter Todd [this message]
2019-04-26 9:38 ` Hampus Sjöberg
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=20190427033227.g5t3p7meztdc6tr4@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=achow101-lists@achow101$(echo .)com \
--cc=ahmerregos@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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