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
-
now, objects have the relation of code and data to drive their organization, which feels like *purpose*. compared to this, classes that only serve as containers for static methods feel empty and fake, bound only by human organizational concerns
1 reply 1 retweet 12 likesShow this thread -
this leads various of my esteemed colleagues to identify such classes as a vile antipattern, feeling instinctively that merely grouping things for their own convenience to be an impure and inelegant motivation unto them i say, verily, thine own self transcend
5 replies 1 retweet 17 likesShow this thread -
Replying to @chaosprime
correct me if i'm wrong but to me the entire point of OOP abstractions is to reduce verbosity by grouping "impure"/"inelegant" styles of data sets/operations within easy-use constructs
1 reply 0 retweets 2 likes
i mean that sounds plausible, i plause the hell out of it
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.