←back to thread

72 points networked | 4 comments | | HN request time: 0.636s | source
1. greatgib ◴[] No.42193395[source]
Typically the kind of library that is useless and root cause of the dependency hell we are now living in.

That kind of simple things should be a basic inside once program or at worse a simple snipper copied from stack overflow or anything like that

replies(2): >>42193503 #>>42197799 #
2. yoavm ◴[] No.42193503[source]
It does not seem to be a library at all, so very little to do with dependency hell. It's something you prepend to your commands if you want them to retry until they succeed. Seems pretty useful to me.
replies(1): >>42193912 #
3. bobnamob ◴[] No.42193912[source]
Also, retries are more nuanced than most people expect, see [1][2]. Getting them right is exactly something I’d appreciate in a library and not something I’d want to reimplement per project/service.

[1] https://brooker.co.za/blog/2022/02/28/retries.html

[2] https://medium.com/yandex/good-retry-bad-retry-an-incident-s...

4. crest ◴[] No.42197799[source]
A non-trivial application should not add a dependency for just exponential backoff + proportional jitter, an easy to use wrapper to put around a quick script is a good idea that and the lack of such a "basic" defensive programming technique has made untold initially small problems a lot worse by creating a thundering herd.