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
I agree that most web code is crap, but if they were forced to use C++ it would still amount to 876 MB due to memory leaks. Nothing short of real AI can force code to be good. Here's Steve Yegge on pitfalls of low level languages and local optimization http://c0de517e.blogspot.com/2009/03/optimization-again-from-steve-yegge.html …
1 reply 0 retweets 1 like -
Replying to @antimule
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
2 replies 1 retweet 3 likes -
Replying to @chaosprime
agree with everything you said. I just think that it also needs to be said that low level langs implicitly teach ppl too much local optimizatiin too early and that is not great either as Yegge noted.
1 reply 0 retweets 1 like -
Replying to @antimule @chaosprime
Can we jump straight to blaming development frameworks that implement seven layers of objects in order to output text to the screen?
1 reply 0 retweets 2 likes -
-
nonono everything in the proper order. you must complain about the poor SQL generation of ORMs first before you move on to complaining about the poor memory management of templating languages.
2 replies 0 retweets 2 likes -
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
1 reply 0 retweets 0 likes
<? ok now it parses
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.