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
tbh if there are different contextual versions of it i don't really think of it as a "utility" method any more. if we have that going on then sure do what you gotta do
-
-
¯\_(ツ)_/¯ ya sure, but the practical distinction is not that big anyway. Lots of Java programmers aggressively mutate static fields.
-
Not my biggest gripe with the “everything through Spring” style either. Endless test run times for running a context for every “unit” test are the worst; only actually needed for low-value tests like “is the HTTP endpoint actually there” too.
End of conversation
New 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.