From: "Hampus Sjöberg" <hampus.sjoberg@gmail•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: Fri, 26 Apr 2019 11:38:03 +0200 [thread overview]
Message-ID: <CAFMkqK94_EqXpdXX4swrWZy+Am-bjvWWR_JFG3JUJxOp1WBZJw@mail.gmail.com> (raw)
In-Reply-To: <CA+PERc0+cUu-0-HsnTNEFY67v2T6BwtV-myjT=mh1i9z5vATYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Bitcoin is a consensus critical system.
We have already had consensus problems between Bitcoin Core-versions,
rewriting everything in another language would expose us to even greater
risks, and moving to a language like Python I see no benefit whatsoever.
Best
Hampus
Den tis 23 apr. 2019 kl 16:47 skrev Ahmer Regos via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org>:
> 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.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1650 bytes --]
prev parent reply other threads:[~2019-04-26 9:38 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
2019-04-26 9:38 ` Hampus Sjöberg [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=CAFMkqK94_EqXpdXX4swrWZy+Am-bjvWWR_JFG3JUJxOp1WBZJw@mail.gmail.com \
--to=hampus.sjoberg@gmail$(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