From: Achow101 <achow101-lists@achow101•com>
To: Ahmer Regos <ahmerregos@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Improving Pre and Post Merging Abilities With Rewriting Core In Python
Date: Tue, 23 Apr 2019 15:23:27 +0000 [thread overview]
Message-ID: <V0VmX7UXCj3jIAzs4ChvyjabCLbjKvyOCURUOoR9q1y0xOcYO8Dl7aMYzIE0qoROqkVZQ4EpxCgD6UA2pBhWM_dfAwvYK7GVZcbs8EoSmW4=@achow101.com> (raw)
In-Reply-To: <CA+PERc0+cUu-0-HsnTNEFY67v2T6BwtV-myjT=mh1i9z5vATYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
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.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, April 23, 2019 4:16 AM, Ahmer Regos via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> I'm proposing re-writing bitcoin codebase in Python for improving pre and post merging abilities, faster operations and better understandability. Python is a fast language with C support, it is good with hashing things, it has a good syntax and everyone can read / understand it unlike C++.
>
> I am willing the coordinate the transformation operation and i believe it would be really good the get rid of C++.
>
> - Ahmer Regos from Regain Beaches.
[-- Attachment #2: Type: text/html, Size: 1674 bytes --]
next prev parent reply other threads:[~2019-04-23 15:23 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 [this message]
2019-04-27 3:32 ` Peter Todd
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='V0VmX7UXCj3jIAzs4ChvyjabCLbjKvyOCURUOoR9q1y0xOcYO8Dl7aMYzIE0qoROqkVZQ4EpxCgD6UA2pBhWM_dfAwvYK7GVZcbs8EoSmW4=@achow101.com' \
--to=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