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
-
-
hey who remembers Smarty that time we decided that we needed to write a templating language in PHP, which is of course a templating language some kind of diabolical inverse nominative determinism going on there
-
<? ok now it parses
End of conversation
New conversation -
-
-
I tend to work with messaging, rather than things that would need ORM. But I think I’ll just switch to languages that are entirely lambda expressions. While still taking the time to beat my head against Bash scripting.
-
well then your goto first complaint ought to be how all message queues suck and lose or misorder messages, or if they're not doing that they're bottlenecking you and causing service worker timeouts all over the place.
-
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.