I mean, “dutonians” from PagerDuty is enough to illustrate how ridiculous this whole thing is

Reading the original comments about being "liable", it felt like another way of saying "there are consequences to your decisions, and as the author you bear some responsibility of what you put out there", which imo is pretty far from how the author of this blog post described it, hence me calling "a pretty big stretch"

But it confirms what I was thinking, going from "liable" to "criminally prosecuted" is a pretty big stretch imo.

> Look if you can't understand that this is a thing that will happen in the real world and that people will potentially suffer as a result you shouldn't be writing a crypto library.

Which is still far from suggesting someone should be prosecuted.

[1]:https://lwn.net/Articles/893327/

[1]: https://shop.jcoglan.com/building-git/

As an outsider, really curious to hear more about this. Is it from an ecosystem point of view, where the "dynamism is disappearing" or more from a day to day, the fact that writing TS is significantly different than writing JS? Or even something else?

Just thought I'd share a example of a use case where the incremental rehashing logic makes sense.

[1]: https://github.com/redis/redis/blob/unstable/src/dict.c

Is there any research to back that? Everything I’ve ready says that it is not a fatality and that it is possible to run, for many years (life?) without destroying your joints.

It’s my understanding that your statement is as accurate as saying “driving a car will result in you getting in a car accident”. It’s extremely possible and it has happened to many people but it doesn’t mean it _has_ to happen

> For my first few sections I wrote the code as I wrote the sections, but then Lak made the suggestion that it would probably be easier to write the code first and then write the chapter

I can echo this a thousand times, I've written the last three chapters this way and this has made a huge difference, wish I had known that earlier!

I will also add that it really made me learn so much because even though I thought I knew quite a bit about Ruby (I knew early on that I didn't know much about Redis). So many times I found myself trying to explain something and realizing that I didn't actually know how it worked and ended up spending hours (days?) researching the inner workings of said thing

PS: Using quotes around book mostly because that's the imposter syndrome kicking in, I was calling it "a series of blog post" for a while, to kinda downplay it

Maybe, I actually have no idea, have you seen numbers?

> Their valuation reflects its use as a cache

How so?

> Did you geo replicate message broker?

No

I've personally mostly used it as a message broker (celery in python, resque in ruby), but it can definitely be used as a database.

Bottom line, it's a very flexible tool, and can be more than "just a cache".