being the kind of hypersystematizing nerd who feels that OOP classes that exist only to contain static utility methods are somehow offensive is relatable, if ridiculous, but once you're doing something = (new someClass())->someUtilityMethod(whatever); you need to be put down
-
Show this thread
-
Replying to @chaosprime
static methods shouldn't require instantiation, though this calls into question the entire point of classes and does tend to inspire lurid thoughts about module systems (or the inadequacies of such as it were)
1 reply 0 retweets 6 likes -
Replying to @danlistensto
yeah, what i'm depicting there is someone who has decided Static Methods Are Bad and is therefore burning malloc pointlessly to be able to call their utility method as an object method
2 replies 0 retweets 12 likes -
Replying to @chaosprime
the mind boggles what shall we tell them about static object reference passing semantics?
1 reply 0 retweets 4 likes
Replying to @danlistensto
i kinda feel like if they could be told anything this pass would not have been reached
12:34 PM - 2 Dec 2019
0 replies
0 retweets
6 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.