Why? Care to explain?
https://aphyr.com/posts/283-jepsen-redis
finally
https://aphyr.com/posts/307-jepsen-redis-redux (see his comments there too)
He had an awesome opportunity to do high concurrency synchronous replication (raft) on top of in-memory databases at a time where ssds were still uncommon, but instead chose to redneck-engineer his own protocol, then double-down that he knows best.
Not that dissimilar to choosing C over rust for familiarity.
Yeah, as usual with devs; pick a tribe then go to insufferable lengths with the newfound and completely unearned superiority complex.
antirez: no, u!
elktown: both sides are tribals with superiority complexes!
Cause he did fuck up, then changed the subject, then claimed the criticism was unfair because he was clearly talking about something else.
It's LLM age. Just port it to Rust if that is so wrong for you. He is doing it for free, no need for arguing about the language he wants to use
Dude asked what's wrong with antirez, I answered
Grandparent wondered whether he was the only one that mistrusts antirez, parent asked for reasons why one would do that, I provided my own.
I used redis multiple times in the past, I have no resentment towards the project or its author(s).
That does not mean that either is above criticism, and I know my freedoms quite well thank you very much.
Feel free to feel insulted!
This is starting to feel less like a developer forum and more like a maga convention.
I think OP wished he had that kind of credit to his name.
And your company took a stab at doing it right [1], though by that point most competent programmers decided that redis was just a smarter memcache and started designing around data loss instead of building on top of the programmable memory system you envisioned.