<a href="https://aphyr.com/posts/307-jepsen-redis-redux" rel="nofollow">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.
aphyr: distributed systems are difficult and break in ways that are difficult to predict, this is known scientific fact and here's a long list of databases I broke because their engineers think the rules don't apply to them.
antirez: no, u!
elktown: both sides are tribals with superiority complexes!
I don't see much wrong with antirez. He does what he does and gives it to the world for free, if you don't like it you are free to roll your own or ignore it. All you are doing here is behaving in a jealous way that makes no sense to me.
Redis remained useful for 10+ years because of the design choices that were made, actually. Many other systems/companies failed since the idea, back then, was that a system needed to be linearizable or could not be useful at all. So what you point as a limit of my work was one of the better things I did in my career.
Thanks, I believe the hate is also linked to my AI-positiveness... Funny enough GPT 6 Astra can easily produce a TLA+ model that can be verified under very real-world system model assumptions on the safety of RedLock, which is a paradox to the arguments I see in this thread and to the AI-rage.
jeffbee · · focus · HN ↗
wg0 · · focus · HN ↗
za_creature · · focus · HN ↗
<a href="https://aphyr.com/posts/283-jepsen-redis" rel="nofollow">https://aphyr.com/posts/283-jepsen-redis
<a href="https://antirez.com/news/55" rel="nofollow">https://antirez.com/news/55
finally
<a href="https://aphyr.com/posts/307-jepsen-redis-redux" rel="nofollow">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.
elktown · · focus · HN ↗
Yeah, as usual with devs; pick a tribe then go to insufferable lengths with the newfound and completely unearned superiority complex.
za_creature · · focus · HN ↗
antirez: no, u!
elktown: both sides are tribals with superiority complexes!
elktown · · focus · HN ↗
za_creature · · focus · HN ↗
Cause he did fuck up, then changed the subject, then claimed the criticism was unfair because he was clearly talking about something else.
tuesdaynight · · focus · HN ↗
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
za_creature · · focus · HN ↗
Dude asked what's wrong with antirez, I answered
jacquesm · · focus · HN ↗
za_creature · · focus · HN ↗
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!
antirez · · focus · HN ↗
jacquesm · · focus · HN ↗
I think OP wished he had that kind of credit to his name.
antirez · · focus · HN ↗