EDIT: or micropayments: https://en.bitcoin.it/wiki/Contracts#Example_7:_Rapidly-adju...
292 karma · joined July 7, 2009
EDIT: or micropayments: https://en.bitcoin.it/wiki/Contracts#Example_7:_Rapidly-adju...
In particular, how old was the version of git they were testing with? Were they using SSDs?
In the end, they only directly added support for 1) type-safe macros, aka "black-box" macros 2) ...invoked transparently as methods, aka "def macros"
They identified "white-box" (non-type safe) macros and quasiquoting as distinct from black-box macros, because the type signature of a black-box macro tells you approximately what it will do, meaning that you can treat it as a "black box". But additionally, in order to write a meaningful type signature, the input to a black-box macro must _already_ be valid scala code! This means that the addition of macros cannot actually result in new scala syntax [d].
[a] https://news.ycombinator.com/item?id=3709193
[b] http://www.infoq.com/presentations/scala-macros
[c] still hoping the existence of scala macros leads to the deprecation of a bunch of other features though
[d] see the explanation starting around 33m30s in [b]
2) As of recently [b], yes... you can add a small amount of junk data
3) When you send a transaction using input address(es) that don't add up to exactly the desired amount, there will be some "change", which needs to go to a new address. Thus, some of your change comes back to you at a new address.
4) Yes, that's possible. But you probably don't want to do that, since it leaks information [c]
----
[a] subject to some limitations: https://en.bitcoin.it/wiki/Transaction_fees#Sending
While it is true that the vast majority of JVM code you interact with is blocking and expects to own whatever OS thread it is running on, that could be treated as a concern of FFI, where untrusted/blocking code in Java land gets dedicated OS threads (similar to FuturePools/execution-contexts for scala Futures, or how you would manually isolate blocking code for Erlang or Go FFI.)
Additionally, the comment dismissing STM seems like an afterthought, because there are at least three JVM implementations (Clojure's, Scala's, and Multiverse)
But the main comment I was referring to was:
To do serious concurrent work in an JVM environment is
different and it will thus require different knowledge
... which suggests that the author isn't interested in supporting Haskell's idiomatic concurrency model atop the JVM, and is instead fine with the status quo of blocking code.If there is a single Bitcoin mining node (out of thousands[0]) that will accept your transaction, you can play.
def complete_items(completed_binindex: Int, bin: ItemBin, nonterminal: Nonterminal, value: Value): MoreItems = {
for {
(item, v) <- bin.items
_ <- expectedSymbol(item)
nextValue <- grammar.nextValue(document, item.origin, bin.binindex, completed_binindex,
nonterminal,item.ruleindex, item.dot, v, value)
} yield {
item.inc -> nextvalue
}I wouldn't say 'big' exactly, but the participation is non-zero: http://blockchain.info/nodes-globe?series=48hrs
1) 'monetary' inflation will decrease, because the rate of bitcoin creation will drop from 7200BTC/day to 3600BTC/day
2) miners will be earning half as much when denominated in BTC
If the decrease in inflation doesn't cause a large enough corresponding increase in price, mining would be less profitable, causing some fraction of miners to drop out, and meaning longer transaction confirmation times (for at most 2 weeks, while the network adjusts to the change in capacity).
My guess is that the huge change in inflation will adequately compensate both miners and investors, and cause a significant enough increase in price to avoid lengthening confirmation time.
https://en.bitcoin.it/wiki/Controlled_Currency_Supply
EDIT: by inflation, I mean 'monetary' inflation, rather than price inflation.
Your 19HcFgnnJseANJAHUjFifVwz68AGYrHc7v address for example, firstbits down to 19HcFgn: http://firstbits.com/
You're skipping the part where she needs to have a bank account, check book, and possibly postage stamps in order to pay her credit card bill.
> ... transfer money (takes 5-7 days) from your bank account...
> ... seller might want to wait until the network confirms a transaction...
She is already familiar with financial institutions taking forever to process payments/clear checks. Additionally, she is familiar with checks bouncing, and with cards being declined.
> Then when you want to pay for something put in the person's bitcoin address
Or, as seen in the linked article, she hits 'Send bitcoins', and then waves her phone at the recipients phone.
> I was one of those people.
It's brave of you to admit that you did not research the thing you invested in. Many of us have.
Do you think that the way the Visa/MC network is implemented is simple enough to explain to someone who does not understand computers? No? Hm, I wonder how people use it...
The point of articles like this is usually to highlight usability improvements for a particular solution, and in this case, to highlight the fact that their is no hardware requirement for bitcoin.
Also, re: the difficulty of acquiring bitcoin: mobile apps like this mean that if one party in a transaction has bitcoin, the other party can go from 0 to 60 on accepting bitcoin in the time it takes to download the app from their app store.
By almost any metric (including value) bitcoin is healthy, and slowly growing: http://blockchain.info/charts
And in the interest of full disclosure: yes, I have an investment in bitcoin, because I truly believe in the strength of the concept.