From: Bernd Jendrissek <bitcoin@bpj-code•co.za>
To: will binns <will@trek•io>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Block Size Debate Analogy / Workaround: Bitcoin is Like Windows 3.11
Date: Sat, 27 Jun 2015 19:36:50 +0200 [thread overview]
Message-ID: <CAF7PVPrQxyCE-zPZxwXfEkWMb0u2cS_nmavBM0b7n7iQdMpFtg@mail.gmail.com> (raw)
In-Reply-To: <558EBCB7.9050100@trek.io>
> In some ways, however, to me at
> least - Bitcoin is like Windows 3.11.
[...]
> Now there is a huge debate about if there
> should ever be a Windows 95, XP, Pro, etc., that scales better and makes
> advances over time, but doesn’t support facets of older versions as it gets
> updated.
I like your analogy for how it frames blockchain compatibility in
terms of the backward compatibility that hopefully most
computer-literate people already understand, but there's a key
ingredient missing.
It's as if, if everyone in the world did somehow upgrade to Windows
95, it would become forever impossible to take a program written *on*
Windows 95 but *for* Windows 3.11, and successfully run it on a
Windows 3.11 computer. It would be as if cross-compilers from Windows
95 to Windows 3.11 didn't, and couldn't, exist. Any coins that have
post-hardfork coinbase outputs anywhere in their tree of inputs (a
Windows 3.11 program, that's written on a computer that has ever run a
Windows 95 program) can never be spent on the no-change side of the
fork.
prev parent reply other threads:[~2015-06-27 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 15:09 will binns
2015-06-27 17:36 ` Bernd Jendrissek [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=CAF7PVPrQxyCE-zPZxwXfEkWMb0u2cS_nmavBM0b7n7iQdMpFtg@mail.gmail.com \
--to=bitcoin@bpj-code$(echo .)co.za \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=will@trek$(echo .)io \
/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