summaryrefslogtreecommitdiff
path: root/MANIFESTO
diff options
context:
space:
mode:
authorantirez <antirez@gmail.com>2019-03-18 15:49:52 +0100
committerantirez <antirez@gmail.com>2019-03-18 15:49:52 +0100
commit3eaa2cdc44a9b0742f0695f44911b92547995836 (patch)
tree66b4d79314d9584f0fe3dfce5cb63164fb898861 /MANIFESTO
parenta5af648fdddaf93e89735a8577b56f12379d1dd2 (diff)
downloadredis-3eaa2cdc44a9b0742f0695f44911b92547995836.tar.gz
MANIFESTO: simplicity and lock-in.
Diffstat (limited to 'MANIFESTO')
-rw-r--r--MANIFESTO6
1 files changed, 5 insertions, 1 deletions
diff --git a/MANIFESTO b/MANIFESTO
index d43a58893..372789462 100644
--- a/MANIFESTO
+++ b/MANIFESTO
@@ -63,7 +63,11 @@ Redis Manifesto
complexity. We'll accept to fight the complexity when it's worthwhile but
we'll try hard to recognize when a small feature is not worth 1000s of lines
of code. Most of the time the best way to fight complexity is by not
- creating it at all.
+ creating it at all. Complexity is also a form of lock-in: code that is
+ very hard to understand cannot be modified by users in an independent way
+ regardless of the license. One of the main Redis goals is to remain
+ understandable, enough for a single programmer to have a clear idea of how
+ it works in detail just reading the source code for a couple of weeks.
7 - Threading is not a silver bullet. Instead of making Redis threaded we
believe on the idea of an efficient (mostly) single threaded Redis core.