From 8c7c25a9fb457f729fe2c190373d156e1816c460 Mon Sep 17 00:00:00 2001 From: Segmond Date: Mon, 7 Oct 2019 15:11:43 -0400 Subject: [PATCH] Update README.md Typo, focuses spelled as focusses Former-commit-id: 40355eac3e46c6e4bb35f5cbc315a05beff291bf --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 18db3c875..538aaf3c2 100644 --- a/README.md +++ b/README.md @@ -18,7 +18,7 @@ On the same hardware KeyDB can perform twice as many queries per second as Redis Why fork Redis? --------------- -KeyDB has a different philosophy on how the codebase should evolve. We feel that ease of use, high performance, and a "batteries included" approach is the best way to create a good user experience. While we have great respect for the Redis maintainers it is our opinion that the Redis approach focusses too much on simplicity of the code base at the expense of complexity for the user. This results in the need for external components and workarounds to solve common problems - resulting in more complexity overall. +KeyDB has a different philosophy on how the codebase should evolve. We feel that ease of use, high performance, and a "batteries included" approach is the best way to create a good user experience. While we have great respect for the Redis maintainers it is our opinion that the Redis approach focuses too much on simplicity of the code base at the expense of complexity for the user. This results in the need for external components and workarounds to solve common problems - resulting in more complexity overall. Because of this difference of opinion features which are right for KeyDB may not be appropriate for Redis. A fork allows us to explore this new development path and implement features which may never be a part of Redis. KeyDB keeps in sync with upstream Redis changes, and where applicable we upstream bug fixes and changes. It is our hope that the two projects can continue to grow and learn from each other.