419 karma · joined October 13, 2012
https://liamzebedee.com
Blockchains allow parties to achieve consensus without trusting any other member. The innovation being that any social system that relies on trust brings with it the problems and implications of the trusted. Common examples include being more costly (overhead/greed), socially exclusionary / corrupt in some circumstances (eg banning protesters). It also facilitates new innovations such as cryptocurrency.
In public blockchains, trust is instead put into the security of the network in terms of its proof-of-work, its developers who maintain the software, the community at large (especially in the case of forks) and so on...
Not mentioned often however is why corporations also are loving the idea of private blockchains (IBM Hyperledger, R3, etc). Private blockchains involve trusting only a couple participants to join the network. A set of banks can define a mutual settlement protocol in a standard smart contract for example - in using a blockchain, they mitigate the risk of other banks affecting their system.
A better example of where a private blockchain would do wonders is in BGP routing. You hear almost every year of a news story where an Indian ISP accidentally broadcasts they forward for Google's IP subnet, and subsequently disrupts all of India's Google access until they manually fix it. A private blockchain among BGP hosts would vastly improve these situations if everyone could agree on which routes they were routing, and globally optimise in the case of failure.
I think the key to achieving anything with the blockchain approach is to not try replace something with a blockchain (ie Facebook) for the sake of removing trust, but pinpointing specific pains that derive from having to trust other parties and then focussing there.
Statistics like these should be more prominent in the argumentation. Regardless of any technical discussion of the merits of SegWit vs. big blocks, there isn't any doubt in the usability of the system as is compared to as before.
I'm interested by your idea, but you would need to work by a different consensus model. Proof-of-stake would be interesting to investigate, since mining doesn't scale with computation power, rather holding of the currency.
> Cocoa Touch is (I suspect) deliberately very simple: there’s Target-Action pattern, Dependency Injection, Delegate and MVC
Can anyone enrich this explanation?
There is a large gap in software for non-linear thinking/sketching. It's not obvious for tasks that require linear thinking, like programming, but when you are trying to explore solutions in an fuzzy problem space, something along the lines of TreeSheets is certainly useful.
Do you mind if I get your email and send you something? Looking at writing about this and would love some feedback.
I agree, insides on the Ethereum tech (like how their proof of work relates to smart contract state, where the DAG fits in) are very brief / difficult to digest at some points.
Ethereum is elegant in many ways - for example, strengthening security by rewarding the linking of orphan blocks in the network. I think there's a need for some better education between the marketing material and War and Peace white/yellow paper ;)
[1] https://github.com/the-laughing-monkey/cicada-platform/blob/...
I don't know about you guys, but my friends spend probably upwards of an hour a day at least.
It's a super cool creative branch of prog research, much of it involving live programming, funky editors/IDEs (Ixi Lang is the macOS rich text editor, where on certain key combos its content is piped and the colours of the editor changed live -- bit of a hack and super cool).
Check some out -- https://www.youtube.com/watch?v=uAq4BAbvRS4
I use it at work on a page-by-page basis-- it drastically reduces the mental overhead of class naming, JQuery spaghetti, maintaining the DOM etc. Sometimes I even surprise myself when something "just works" because of React's well-controlled model.
The cognitive load of using plain React is unparalleled for me. The effort to setup the tooling is a bit of a hassle though..
Correct me if I'm wrong, but this poses a problem if you ever want to take WebRTC further (i.e. in a self-hosted mesh network).
[1] https://en.wikipedia.org/wiki/Mathematical_universe_hypothes...
[2] http://www.osti.gov/scitech/servlets/purl/28404/