there seems to be this common junior-to-midlevel programmer thing where they got confused once by static vs. instance methods so they decided that static methods are MORALLY WRONG and we have to do (new Foo()).bar() for everything even if it has zero interaction with object state
-
Show this thread
-
Replying to @chaosprime
This sounds absurdly costly for bad ergonomics depending on constructor and way the language allocates memory unless the compiler anticipates such stupidity.
2 replies 0 retweets 3 likes
Replying to @xiphiness
strong agree i kind of have to restrain myself from going on tirades all the time about how """modern""" languages train people to treat malloc as a free operation
11:25 AM - 16 Sep 2019
0 replies
0 retweets
4 likes
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.