summaryrefslogtreecommitdiff
path: root/78/81412a2d38c5b339a90dbb63674f46c63160e7
blob: d063fd396270a699615253c9cec8578927fe4dc1 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
Return-Path: <will@trek.io>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id C4CF4BC8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 15:09:59 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yk0-f171.google.com (mail-yk0-f171.google.com
	[209.85.160.171])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 08D14F2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 15:09:58 +0000 (UTC)
Received: by ykdr198 with SMTP id r198so81960564ykd.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 08:09:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=trek.io; s=google;
	h=message-id:date:from:user-agent:mime-version:to:subject
	:content-type; bh=E9VwReejKliW+tsyDITzLFGjzY8tUsOW+fKVKqLHJY4=;
	b=Oi3GS0I53tDbQG34qzVYlyLFo62E3H22Ci+ACuU8r7neuNlvgWOkqB6XoTobdhGHQT
	gXRCxjyCNGAQyswOiTtlOcA+nRoecQXeE6QNw0arqVhflrEV/U+1QQHnCqAVfNmkGFcv
	im48mMUPXeRAgbA/bsDo/hsYM4ksDPj3lw1bo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
	:subject:content-type;
	bh=E9VwReejKliW+tsyDITzLFGjzY8tUsOW+fKVKqLHJY4=;
	b=MM7x34U64PsSxxxbKsgcC4GMfua7Q2kqqyWbExbP4jYgl+wsHVQ4IYJ8lcZZ3vhO2d
	MUgwr719S7Oo0ghXGHMhIsyPWpv4LDkgb4eup+X3beLFT1raIjHYmXgZpGfqXpEF1uZZ
	d2kZJVKS4IIQrW95/zsnOmWxTWmKD/9YPlzWDdR4ImyPcXsinkSHLwu1EhUuBoPlx4k6
	buhgJf5AG7Pkmxgma5sHUzsOu32+XZEdBIecI0K6tUlX2FsOGOi1P5/I2SdsBfbkxqPh
	YHOcDGrAbAWCVk/5rFgma/v/KBOdv4+7sKOWto/glGrmxbZnE4pR4RjCx4SqO85vy8JQ
	wLgw==
X-Gm-Message-State: ALoCoQkBnR3Z7V6TBVfG5RjQn4GAmrGinANThB9W7LLF4UWp0mix4c/rpUwh4uXOHXMElQVzwjiW
X-Received: by 10.13.220.66 with SMTP id f63mr7959707ywe.63.1435417797848;
	Sat, 27 Jun 2015 08:09:57 -0700 (PDT)
Received: from GWB3.local (ip112-154-64-186.ct.co.cr. [186.64.154.112])
	by mx.google.com with ESMTPSA id
	y84sm29838870ywd.28.2015.06.27.08.09.55
	for <bitcoin-dev@lists.linuxfoundation.org>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Sat, 27 Jun 2015 08:09:56 -0700 (PDT)
Message-ID: <558EBCB7.9050100@trek.io>
Date: Sat, 27 Jun 2015 09:09:43 -0600
From: will binns <will@trek.io>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
	rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="290tjbeo1PrTPOKU8txhheFkihnkhGw4v"
X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	HTML_MESSAGE, RCVD_IN_DNSWL_LOW,
	T_DKIM_INVALID autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: [bitcoin-dev] Block Size Debate Analogy / Workaround: Bitcoin is
	Like Windows 3.11
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jun 2015 15:09:59 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--290tjbeo1PrTPOKU8txhheFkihnkhGw4v
Content-Type: multipart/alternative;
 boundary="------------050801030804060804090708"

This is a multi-part message in MIME format.
--------------050801030804060804090708
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hello all, I wanted to add another analogy here to this block size
debate, in case helpful. I understand some may not see it this way, so
apologies in advance if it ruffles anyone's feathers. In some ways,
however, to me at least - Bitcoin is like Windows 3.11. Before Bitcoin
everything was DOS - something completely disruptive and good for
society has come into the computing space that exponentially improves
upon almost everything in the space that existed before it. 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=E2=80=99t supp=
ort
facets of older versions as it gets updated.=E2=80=8A What will happen to=
 3.11
users/developers/etc. who don't upgrade that have money and/or important
tech tied into the 3.11 platform? Should it just be Windows 3.11 forever
except with better programs that continue to be built to run on it? Or,
should we agree to only change it if 100% of Windows users or Windows
developers agree on upgrading?

Regardless of what side we all stand on, I just want to point out that
this mailing list is full of incredibly brilliant minds leading the
charge into perhaps one of the greatest technical achievements in recent
decades. Maybe it would be a good idea for each side of the issue here
to democratically appoint a developer representative, and then allow the
representatives to achieve a framework and hammer out the details of the
solution together?

Hope you all have nice weekends,
Will

--=20
// will binns
// gpg fingerprint: 4519 7EB7 66A7 CC5E 4E66 F200 AF5C 2D1C E58E B37C
// threema id: 5YM2J894


--------------050801030804060804090708
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>

    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf=
-8">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <font size=3D"-1">Hello all, I wanted to add a</font>nother analogy
    here to this block size debate, in case helpful. I understand some
    may not see it this way, so apologies in advance if it ruffles
    anyone's feathers.
    <meta charset=3D"utf-8">
    <span style=3D"color: rgba(0, 0, 0, 0.8); font-family:
      jaf-bernino-sans, 'Lucida Grande', 'Lucida Sans Unicode', 'Lucida
      Sans', Geneva, Verdana, sans-serif; font-size: 14px; font-style:
      normal; font-variant: normal; font-weight: normal; letter-spacing:
      -0.360000014305115px; line-height: 18.2000007629395px; orphans:
      auto; text-align: start; text-indent: 0px; text-transform: none;
      white-space: normal; widows: 1; word-spacing: 0px;
      -webkit-text-stroke-width: 0px; display: inline !important; float:
      none; background-color: rgb(255, 255, 255);">In some ways,
      however, to me at least - Bitcoin is like Windows 3.11. Before
      Bitcoin everything was DOS - something completely disruptive and
      good for society has come into the computing space that
      exponentially improves upon almost everything in the space that
      existed before it. 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=E2=80=99t support facets of old=
er
      versions as it gets updated.=E2=80=8A What will happen to 3.11
      users/developers/etc. who don't upgrade that have money and/or
      important tech tied into the 3.11 platform? Should it just be
      Windows 3.11 forever except with better programs that continue to
      be built to run on it?</span> Or, should we agree to only change
    it if 100% of Windows users or Windows developers agree on
    upgrading?<br>
    <br>
    Regardless of what side we all stand on, I just want to point out
    that this mailing list is full of incredibly brilliant minds leading
    the charge into perhaps one of the greatest technical achievements
    in recent decades. Maybe it would be a good idea for each side of
    the issue here to democratically appoint a developer representative,
    and then allow the representatives to achieve a framework and hammer
    out the details of the solution together?<br>
    <br>
    Hope you all have nice weekends,<br>
    Will<br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
// will binns
// gpg fingerprint: 4519 7EB7 66A7 CC5E 4E66 F200 AF5C 2D1C E58E B37C
// threema id: 5YM2J894</pre>
  </body>
</html>

--------------050801030804060804090708--

--290tjbeo1PrTPOKU8txhheFkihnkhGw4v
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJVjrzCAAoJEK9cLRzljrN8TpsP/RWhdOGsd8jQaBSyizCwvWqG
FCvVvQlwabZIFIy4gNyfCcf0J6x5qKf4tH9/AJDI0mrFt2yQx+TT7wkejFnK8Qup
/P6H91XvCH6i0VL/WsdU6G35A9bDjcR6sjkMVIgjLYwgYUxM1nfId4oYHkvO8GMy
n0GaOIKsLJAkeq3K6m0J+aEAWAVVGL4gaHYFmbER2cJk6IilWOQFF+OlqPsIUSPm
FXEEAYJOB+/wIWtu4UfWLkaoEBPudRObZazbPnWX36sVSdDYHxR01axpiYrlr63h
C5R18R5DJ4UcBNLv/MF3el1NofKCkPKsNLR1WxZHFblDyQBc5AbNC3cJxh8PSkxJ
JATdJAvQrEI7srtchYa7sTkdTBXDriYEXjvVNtvq2Lio7x4145ea5eQOzvAwyqvl
6WgqHcOzG1XpdOkqblP94dV6aDiMBs3t/eCXarTxO3N143CWT7sq6id1poWGxdmp
ddOI7IE8gDl/6yBZzmiahhv8J7SdPFFPeQQjaHkKKbDWRGVSqlwA61jEPLnPLvDp
S2iwo7otin1g9rY0fnVHdK9FKfo9RbpITuzOYfolUCfwwXN+lBotvwb8qdB5WPNp
k6Q6l2/5Ixk8Gz/cXFumGukrb7VNKpwYYhpO7VqhR15PUdLwbjAFhtq8DWTjuj33
c8tCJzhyCmWH6EuDmFtP
=UWwB
-----END PGP SIGNATURE-----

--290tjbeo1PrTPOKU8txhheFkihnkhGw4v--