From: Aaron Axvig <aaron@axvigs•com>
To: "'Wladimir'" <laanwj@gmail•com>, "'Chris Pacia'" <ctpacia@gmail•com>
Cc: 'Bitcoin Dev' <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] "bits": Unit of account
Date: Tue, 22 Apr 2014 08:51:42 -0500 [thread overview]
Message-ID: <BLU406-EAS319EB73C2094DBD7D04D981D4590@phx.gbl> (raw)
In-Reply-To: <CA+s+GJBWwstMjKR-A6RyyaA3S4E1d_qapMzyrFkgHNxp__XqDg@mail.gmail.com>
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
next prev parent reply other threads:[~2014-04-23 5:12 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 [this message]
2014-04-23 9:44 ` Danny Hamilton
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=BLU406-EAS319EB73C2094DBD7D04D981D4590@phx.gbl \
--to=aaron@axvigs$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=ctpacia@gmail$(echo .)com \
--cc=laanwj@gmail$(echo .)com \
/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