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
"Class that's just a container for static methods" is an antipattern, but it's one that Java/C# give you no tools to solve
1 reply 0 retweets 2 likes
Replying to @alexkyllo
it's fine PHP solves that with global functions classes that are just containers for static methods are fine
9:30 AM - 16 Sep 2019
0 replies
0 retweets
1 like
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.