# Decentralization theory

2018-04-13

> The learning-curve of any decentralization technology is inversely related to its adoption-rate.

> Faced with the dilemma of running their own version versus using existing infrastructure, the user will always choose the latter for convenience.

> Expanding on the theory:

> - When referring to adoption-rate of the technology, it is the actual managing of the servers to keep in mind
> - When referring to choosing existing infrastructure due to convenience, it is end-users we should keep in mind
> - Each sentence is its own separate theory, but they are related

> Decentralization Dilemma (cache)

I am thinking a lot about convenience (cache) these days and all the implications and intrications it drives, I will probably write a whole article about that given how fondamental it is in our society. Centralization is required to achieve convenience which has an incidence on everything.

Réponse de Karl (cache) et article promis.

Other articles in English: On caching links, Bushcraft retrospective, Into the Raft, Into the Bugs, Meritocracy crisis, The Seller, the Teacher and the Wise, Into the Good, Into the Mice, Into the Camp, Into the Wind, Into the Snow, Into the Cold, Async Python Frameworks, Distributed teams, Into the Wild, Without JavaScript, Inclusive Python, Micro-cultures and governance, Resilient Web and Tools, Bitcoin and energy, Team building, Inclusive developer, Cultural Intimacy, Tools and teams, Senior developer, Slow Data, Inclusive communities, Delivery and value(s), Collaboration debt, Communities and leadership, Specifications and APIs. Oh, and most of the 2018 thoughts.