From: Danny Hamilton <danny.hamilton@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] "bits": Unit of account
Date: Wed, 23 Apr 2014 04:44:55 -0500 [thread overview]
Message-ID: <CAJ=FHudD3uD7oYqHyhMQJaGH5GntfD0_mYZTKXU_pFTerdJuow@mail.gmail.com> (raw)
In-Reply-To: <BLU406-EAS319EB73C2094DBD7D04D981D4590@phx.gbl>
[-- Attachment #1: Type: text/plain, Size: 3841 bytes --]
It seems to me that xbit is no more distinct or intuitive than µbit. In
either case it's simply an arbitrary character in front of the word "bit".
Of course, for the majority of the world familiar with SI, the µ actually
adds additional meaning that is lost with the x.
Furthermore, given the multiple concerns voiced about the overuse of the
word "bit", µBTC seems to solve the problem.
Since we are talking about how it would be displayed in software, we don't
need to be concerned about how people will pronounce it, or what the
nickname will be. If most of the wallets start displaying amounts in µBTC
quantities, it will be obvious that a µBTC is a different magnitude than a
BTC. Nobody is going to look at their 100,000 µBTC balance and think they
have 100,000 BTC. People will immediately make the mental adjustment to the
new order of magnitude even if they don't specifically know that µ means
micro, or that micro means 1e-6.
Nicknames will form organically (much like buck, fin, large, k, grand, and
benny for U.S. currency), I've always been partial to milly (or millie) and
mike (or micky) as nicknames for mBTC and µBTC. I've personally used those
when speaking with people, and they seem to catch on pretty quickly.
As has already been mentioned, you're going to be hard pressed to find
software that denotes U.S. balances in "bucks". There isn't any good
reason to be coding a nickname like "bit", "xbit", or "mike" into wallet
software.
- Danny Hamilton
On Tue, Apr 22, 2014 at 8:51 AM, Aaron Axvig <aaron@axvigs•com> wrote:
> That piece of horse equipment is called a bit in the US too. But the point
> stands: most people don't use "bit" on a daily basis other than referring
> to
> "a little bit of <something>."
>
> -----Original Message-----
> From: Wladimir [mailto:laanwj@gmail•com]
> Sent: Sunday, April 20, 2014 11:27 AM
> To: Chris Pacia
> Cc: Bitcoin Dev
> Subject: Re: [Bitcoin-development] "bits": Unit of account
>
> On Sun, Apr 20, 2014 at 6:19 PM, Chris Pacia <ctpacia@gmail•com> wrote:
> > The term bit is really only overloaded for those who are techy. 95% of
> > the population never uses the term bit in their daily lives and I
> > doubt most could even name one use of the term.
> > Plus bit used to be a unit of money way back when, so this is kind of
> > reclaiming it. I think it's a great fit.
>
> That's a very anglocentric way of thinking.
>
> Here in the Netherlands, a "bit" is something you put in a horses's mouth.
> It's also used as imported word (in the information sense).
> We've never used the term for money.
>
> Wladimir
>
>
> ----------------------------------------------------------------------------
> --
> 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
>
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 5139 bytes --]
next prev parent reply other threads:[~2014-04-23 9:45 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 12:35 Mike Gehl
2014-04-20 13:15 ` Rob Golding
2014-04-20 14:28 ` Tamas Blummer
2014-04-20 14:52 ` Christophe Biocca
2014-04-21 8:52 ` Thomas Voegtlin
2014-04-21 9:34 ` Tamas Blummer
2014-04-22 14:55 ` Natanael
2014-04-20 14:53 ` Pieter Wuille
2014-04-20 15:05 ` Tamas Blummer
2014-04-20 15:50 ` Alan Reiner
2014-04-20 16:19 ` Chris Pacia
2014-04-20 16:27 ` Wladimir
2014-04-20 16:30 ` Chris Pacia
2014-04-22 13:51 ` Aaron Axvig
2014-04-23 9:44 ` Danny Hamilton [this message]
2014-04-23 9:56 ` Tamas Blummer
2014-04-23 11:48 ` Chris D'Costa
2014-04-20 16:23 ` Erik Garrison
2014-04-20 16:30 ` Alan Reiner
2014-04-20 16:56 ` Mike Caldwell
2014-04-20 17:47 ` Jannis Froese
2014-04-20 18:10 ` Pavol Rusnak
2014-04-20 17:42 ` Arne Brutschy
2014-04-20 18:11 ` Mike Caldwell
2014-04-20 18:22 ` Arne Brutschy
2014-04-20 18:34 ` Mike Caldwell
2014-04-20 18:43 ` Oliver Egginger
2014-04-20 19:19 ` Christophe Biocca
2014-04-20 19:32 ` Gmail
2014-04-20 20:28 ` Mike Caldwell
2014-04-21 0:16 ` Justin A
2014-04-21 1:18 ` Mike Caldwell
2014-04-21 1:33 ` Un Ix
2014-04-21 3:34 ` Mike Caldwell
2014-04-21 4:08 ` Christopher Paika
2014-04-21 5:41 ` Pieter Wuille
2014-04-21 5:51 ` Tamas Blummer
2014-04-21 6:21 ` Tamas Blummer
2014-04-21 12:14 ` Un Ix
2014-04-21 12:24 ` Tamas Blummer
2014-05-01 22:35 Aaron Voisine
2014-05-03 2:06 ` Gordon Mohr
2014-05-03 5:41 ` Aaron Voisine
2014-05-03 15:48 ` Christophe Biocca
2014-05-03 16:02 ` slush
2014-05-03 16:10 ` Tamas Blummer
2014-05-03 16:27 ` Mike Caldwell
2014-05-04 1:04 ` Chris Pacia
2014-05-04 5:18 ` Drak
2014-05-04 6:15 ` Aaron Voisine
2014-05-04 6:23 ` Un Ix
2014-05-04 6:27 ` Wladimir
2014-05-04 6:36 ` Tamas Blummer
2014-05-04 6:59 ` Wladimir
2014-05-04 14:42 ` Mike Caldwell
2014-05-05 22:33 ` Gordon Mohr
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='CAJ=FHudD3uD7oYqHyhMQJaGH5GntfD0_mYZTKXU_pFTerdJuow@mail.gmail.com' \
--to=danny.hamilton@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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