Thanks coleifer, I understand that the current development path may look odd, but it's definitely not the first time: the critiques for Lua scripting or Pub/Sub where much stronger AFAIK :-) However I want to really share what is the process behind and why certain features like ACLs are so important (for reasons very different than the ones you may guess I think, that is, no enterprise customers in need for security), and why RESP3 has out-of-band data channels support (even if they are not implemented by the server). I'll write a blog post today, and reply here with the address. Cheers!
Thank you for taking the time to respond so thoughtfully to my comment. If I had been talking directly to you, I hope I would have written something less entitled and expressed more gratitude for the gifts you've given the community, and which you continue to improve.
Redis is exactly the kind of software that gives me joy. Aesthetically and intellectually. Its pieces are orthogonal -- a word you used in your blog post. The code is small, tight, and well designed. It invites you to think more creatively. The lolwut command was also a very good innovation!
Your comment was already great. It was the comment of somebody that cares about Redis and is closely observing what direction it is headed. Also I went through your own set of questions exactly and decided to do certain things after some consideration: it's not obvious at all if this was the right decision but at least the process can be made transparent. Thanks!
P.S. I'll also address threading and persistence.