|
Another speaker from the event here, and totally in agreement w. hashset. I've attended that session and have had the pleasure of being exposed to Matt's views in other occasions (IRL and online :)). While I don't necessarily agree with everything Matt says, his perspective is unique - he's the only 0.5 core Redis developer in the world and his contributions to the project are mostly inspiring and certainly of quality. From what I've seen, he's devoted to Redis as much as anyone can be and takes the project very (too?) personally. Matt's presentation skills are also kinda unique - he uses at least 2^32 slides in every talk, and these are mostly filled with cartoons/memes that I'm too old to recognize mixed with geeky jokes that he makes up by himself ("What is the favorite food of villains? configs." - brilliant!) (remember that even making up a bad joke takes considerable talent.) However, between the puns and laughs, his talk is honest and his messages are clear. He usually (I missed the first 2m of this session [i.e. first 200 slides] but I'm guessing he did it this time as well) opens with an apology for his upcoming rants. Then he delivers sharp criticism at what he perceives to be faults based on his 1st-hand experience. Instead of accepting the "facts", he challenges them and tries suggesting creative approaches to solving these problems. Yes, he could be a better politician but maybe he doesn't want that (anymore?) - it seems that he wants to make the (Redis) world a better place by acting. He uses shock to deliver his points, and perhaps that's excessive at times, but I give him the credit because he tries practicing what he preaches. Matt has his reasons for choosing this rhetorical style - maybe he'll change it after this experience (although mostly likely he won't) - and quoting out of context is often ill-perceived even when well-intended, but when you listen to what he says rather than the how, he certainly shines a hard and clear light on some uncomfortable facts. Perhaps these [facts] are immutable, perhaps they can be tweaked and optimized for joy - I can't claim I know any better... but he definitely stirs things up and ignites thought-provoking discussions... and perhaps that's all that's needed. I don't think Salvatore should or can be "replaced" by Matt, or by anyone else for that matter, until if and when Salvatore decides so. I don't believe that anyone with an IQ above 42 seriously thinks that Salvatore hasn't been or isn't committed to Redis. I didn't interpret Matt's talk as a coup attempt but rather as the continuation to previous discussions about scaling Redis' development. I can't imagine Matt was thinking that he'll be overthrowing the Benevolent Dictator during Redis Conf's last session - my impression of the talk was that in his own Matt-ish way, Matt was trying to shock everyone, and specifically antirez, into action to better things. It is the maintainer's right and obligation to choose between merging, cherry-picking from or even entirely rejecting Matt's orally-submitted PR, but I really don't see that PR meant as a personal attack. My 2c. |
for me actually the problem is totally a different one, that Matt’s rants have a lot of slides and jokes but no clear arguments or no arguments I recognize as valid. I’ll show point by point his arguments and why they are IMHO flawed. The thing is, between jokes and memes, and putting some random argument that “looks” have some merits inside, it is easy to fake a sensation of “real content” that is not there.
Examples of his points and why I believe they are wrong.
1. Redis is too complex and has too many components and protocols.
The programming community begs to differer. Redis is an example of a non trivial system software that a single individual can understand and modify easily. Matt points as "thins to parse" to CSV fields with a space inside, and as a "yet another protocol" to the cluster bus that uses a C structure sent over the wire, for which using the normal Redis client protocol would be extremely suboptimal.
2. We have obligations towards Redis users but for Salvatore Redis is hobby++.
Actually his vision about merging stuff liberally is exactly the irresponsible practice that should be avoided. Not only he does not spend time to improve the basis and doing serious code reviews to other peoples code (or if he does, it does not show up), but also often his own code is written in an informal way without understanding the cascading side effects he could have. Yet he focuses on adding things to Redis, not checking what the bugs could be. There are other people contributing in a different way. For example Sun He fixed a number of issues in Matt's quicklist code just reading the code as soon as the code was posted. To be responsible is to write sane code, and especially, instead of writing just new code, focusing a lot into fixing existing code. Another thing that is for me extremely odd is fixing things with a commit that happens to work, and commenting that it apparently works but the reasons are not clear and hand waving about a "possible" cause. For me this is not system programming.
3. Focusing for 5 minutes on the README -> README.md switch is just not having points.
4. Delay of Redis Cluster.
Even if this was addressed many times with: we had a not good enough single-node story to focus on Cluster so this was delayed many times is apparently not enough. It is clear and obvious, so citing this again and again is just an attempt to find an argument to attack.
(there is more but useless to continue -- it is clear it's a very different POV)
So what to do to improve Redis? To do the actual work that is hard to do, reviews, fixes, small incremental improvements, submitting code that is designed well in the first instance, and so forth. Shocking talks are just a useless display of memes.