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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <abrutschy@xylon.de>) id 1WbwOU-00079G-Mm
for bitcoin-development@lists.sourceforge.net;
Sun, 20 Apr 2014 18:23:10 +0000
X-ACL-Warn:
Received: from mxin.ulb.ac.be ([164.15.128.112])
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WbwOR-0005B0-EC for bitcoin-development@lists.sourceforge.net;
Sun, 20 Apr 2014 18:23:10 +0000
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsYDAFYQVFNYRG20/2dsb2JhbAANS4NVvSOHOQECgTGDGQEBAQQBAQFnAwEEBgEQCw4KCQwKDwkDAgECARUBLwYNAQUCAQGISqhoo3cXjG+BcwcKhC4ElhaCWIZBj0E
Received: from dslb-088-068-109-180.pools.arcor-ip.net (HELO [192.168.178.31])
([88.68.109.180])
by smtp.ulb.ac.be with ESMTP/TLS/DHE-RSA-AES128-SHA;
20 Apr 2014 20:22:51 +0200
Message-ID: <53541079.9000909@xylon.de>
Date: Sun, 20 Apr 2014 20:22:49 +0200
From: Arne Brutschy <abrutschy@xylon.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Mike Caldwell <mcaldwell@swipeclock.com>
References: <CAJKMfeQO6pyi5b-83FyMSHcq0Sa1QkP+RouQVBdCYPtXXboY8A@mail.gmail.com> <53540715.7050803@xylon.de>
<1C408C12-B39B-46E4-B997-153D566158B1@swipeclock.com>
In-Reply-To: <1C408C12-B39B-46E4-B997-153D566158B1@swipeclock.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1WbwOR-0005B0-EC
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] "bits": Unit of account
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 18:23:10 -0000
I agree that overloading isn't an issue when necessary, but my point was
that the necessity is lacking. If we're free to pick anything, why pick
something that is overloaded?
Moreover, "bit" is an abbreviation of bitcoin and might be confused with
it. Most currencies use a work that is phonetically very different and
short, so why not do the same?
Pluk, or cred, or finney (as proposed the thread I posted), or
whichever. We could call it "unsp" for unspent ;)
Arne
On 20/04/14 20:11, Mike Caldwell wrote:
> It is a paradigm that is easy to explain and grasp for neurotypical
> people.
>
> The average mind has no problem overloading words and distinguishing
> the intended meaning from context. For most people, overloading a
> single syllable word with a new meaning is much less complicated than
> using a unique 3+ syllable word like satoshi or micro-anything.
>
> Doing software development warps our minds to demand fully qualified
> names for everything. We know our compilers would say "bit? Fatal
> error 0xaaabbbbwtf, can't continue, not sure if you mean a Boolean or
> a dog bite". But this peculiarity should not be projected onto the
> people we are trying to get bitcoin to appeal to, not if we want them
> to feel like we think about their experience.
>
> If I were to say "a Bitcoin can be divided into a million bits", less
> than 0.1% of average joes would think I was talking about German
> beers or the thing that goes in horses mouths. Really, most people
> are good at using context to relate this to "a dollar can be divided
> into 100 cents" and accepting it. This requires much less of their
> mind resources than using SI prefixes correctly or learning 3
> syllable words that (to them) have no instantly apparent relationship
> to Bitcoin.
>
> Mike
>
> Sent from my iPhone
>
> On Apr 20, 2014, at 11:44 AM, "Arne Brutschy" <abrutschy@xylon.de>
> wrote:
>
>>> I propose that users are offered a preference to denominate the
>>> Bitcoin currency in a unit called a bit. Where one bitcoin (BTC)
>>> equals one million bits (bits) and one bit equals 100 satoshis.
>>
>> There have been many proposals for more or less arbitrary subunits.
>> What would be the merit of your proposal? I don't really follow the
>> reasoning that it's better if it's uncommon for everyone rather
>> than just uncommon for people not used to metric units.
>>
>> Regarding the label of a "bit": I have to agree with the others
>> that bit is heavily overused as a unit, but I am a computer
>> scientist, so I don't have the "average joe's" perspective on this.
>> I find it weird to use as it's already in use in English - "a bit
>> of work" etc
>
> ------------------------------------------------------------------------------
>
>
Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and
> their applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________ Bitcoin-development
> mailing list Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
|
