|
|
|
|
|
|
by ajlburke
1677 days ago
|
|
|
I liked his point near the end of the article comparing blockchains to XML - overcomplicated and oversold and added to too many things due to marketing and consultant hype. The obvious next question he didn't ask is, what is the JSON of blockchain? The one that's more flexible and efficient and ends up actually becoming ubiquitous? Maybe it hasn't appeared yet? Maybe it shouldn't? I don't know, but the comparison is just waiting for that followup. |
|
|
> Here's a metaphor. Blockchains today are like… XML in the early 2000s. A long-burning overcomplicated trash fire that a bunch of large, cash-rich, unscrupulous, consultant-filled mega-organizations foisted on us for years and years, that we all now pretend we weren’t dumb enough to fall for. Remember SOAP? Remember when we tried to make HTML4 into XHTML? Ew, no.
To answer your question, here are some suggestions for what might be the JSON of blockchain:
* Git - Cryptographic hashing, Merkle trees, and distributed architecture (pre-GitHub) to record a history of events.
* Databases (SQL, NoSQL, NewSQL) - Have been running the entire fincancial system for several decades.
* Credit cards - ubiquitous electronica payments "Credit card was the most used payment method in the United States in 2020, with 38 percent of point of sale payments being made by credit card." - statista.com
* Apple/Samsung/Google Pay & friends.