i'm sure it's a coincidence that we decided it was too much to ask for programmers to handle memory allocation and twenty years later if you leave a social media website tab open for a day now it's using 876 MB of memory
-
-
Sounds like a) you’ve worked with the wrong message queue servers and/or b) you haven’t worked with properly tuned queue connection pools, Also... requiring that messages are read in order requires a single queue reader ... which is a bottleneck. Also, kafka.
-
i'm just being grumpy because the theme of the thread is complaining about bad software. none of this is meant to be taken seriously. we use tools because they mostly work fine and 99% of the time do what we need them to do.
-
De nada.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.