honestly, we don't actually need programmers to manage memory C++ style, we just need them to be *able* to. the real problem is that GC languages implicitly teach people that malloc is a free operation and therefore teach them to waste it absolutely firehose-style
-
-
-
if you just dial that back *moderately* instead of writing everything as fluent transformations that allocate twelve intermediary data structures because those look nicer than crusty old for loops in your IDE, the results are tremendous
- 2 more replies
New conversation -
-
-
Can we jump straight to blaming development frameworks that implement seven layers of objects in order to output text to the screen?
-
heck yeah
- 3 more replies
New conversation -
-
-
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.
-
you know what we call problems that show up after more than 5 minutes of runtime? "not part of the demo"
End of conversation
New conversation -
-
-
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?
-
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
End of conversation
New conversation -
-
-
This Tweet is unavailable.
-
thank you for your service
End of 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.