From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id C4CF4BC8 for ; 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 ; Sat, 27 Jun 2015 15:09:58 +0000 (UTC) Received: by ykdr198 with SMTP id r198so81960564ykd.3 for ; 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 (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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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 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? 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-- --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--