When GoLang was first announced, it began an never-ending amount of confusion for me (a Go board game player), as I started to see all these articles around Go on HN, just to be continually disappointed.
And all of the architects here have probably bemoaned the sudden shift in interest when "architecture" inevitably refers to software and nothing about buildings. (Though excitement for both is certainly not mutually exclusive!)
Sometimes it's just a funny way of getting introduced to something that's really cool.
"Our consensus process uses peering ... instead of mining. The ledger is a data structure that describes the current state of the network as a merkle tree"
As a mobile developer, these Ripple articles always trick me because to us Ripple is the fastest emulator for testing PhoneGap apps (HTML5 that runs on multiple mobiles wrapped inside a native app). An emulator for PhoneGap that runs in Chrome as a plugin basically.
From a mobile dev perspective this other Ripple is some worthless alternative payment method no one uses because PayPal has all the accounts so is easier for the user, or iTunes or Google or amazon or Samsung Fusion payments are built into their stores and protected by TOS as being the only payment processor you can use.
So an article on another payment method is pretty worthless and the name collision is pretty annoying because I have to sometimes follow the link before I see it for what it is.
Comments
When GoLang was first announced, it began an never-ending amount of confusion for me (a Go board game player), as I started to see all these articles around Go on HN, just to be continually disappointed.
As a Mesh Networking Practitioner, I see I'm once again going to have to deal with namespace collision. (Ripple has been well used name in another domain: http://www.ietf.org/proceedings/75/slides/roll-2/roll-2_file...)
Interesting - Ripple the routing protocol is primarily about Directed Acyclic Graphs, while Ripple, the payment network, works with merkle trees.
Combine the two concepts together, a directed acyclic graph of tags stored as a merkle tree, and you basically have git.
And all of the architects here have probably bemoaned the sudden shift in interest when "architecture" inevitably refers to software and nothing about buildings. (Though excitement for both is certainly not mutually exclusive!)
Sometimes it's just a funny way of getting introduced to something that's really cool.
Ripple-the-payment-method is about routing through directed networks. Merkle trees are not really related to the payment mechanism at all.
From the article:
"Our consensus process uses peering ... instead of mining. The ledger is a data structure that describes the current state of the network as a merkle tree"
And still, merkle trees are not really related to the payment mechanism.
As a mobile developer, these Ripple articles always trick me because to us Ripple is the fastest emulator for testing PhoneGap apps (HTML5 that runs on multiple mobiles wrapped inside a native app). An emulator for PhoneGap that runs in Chrome as a plugin basically.
From a mobile dev perspective this other Ripple is some worthless alternative payment method no one uses because PayPal has all the accounts so is easier for the user, or iTunes or Google or amazon or Samsung Fusion payments are built into their stores and protected by TOS as being the only payment processor you can use.
So an article on another payment method is pretty worthless and the name collision is pretty annoying because I have to sometimes follow the link before I see it for what it is.
When GoLang was first announced, it began an never-ending amount of confusion for me (a Go board game player)
I know what you mean, I love Ripple chocolate bars. ;)