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
-
-
Replying to @chaosprime
thinking about it backwards. it's using 875MB _with_ an automatic garbage collector trying to free up whatever it can. now imagine how much memory it would use if there wasn't even a GC?
2 replies 1 retweet 16 likes -
Replying to @danlistensto
that definitely makes up for teaching a generation of developers (who i was going to call coders but the word turned to ashes in my mouth) that malloc is a free operation
0 replies 0 retweets 14 likes -
Replying to @Aelkus @chaosprime
certainly that. the insensitivity to most forms of performance of users is the real story though. twitter has atrocious performance and requires me to actually hard refresh the page about once every 10 minutes because of memory problems. i don't care though, i just refresh.
3 replies 0 retweets 11 likes
you know what we call problems that show up after more than 5 minutes of runtime? "not part of the demo"
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.