Dependency Injection

what did you just say about me

Why is it bad? It has its place. Like when you write a callback that can be provided a bazillion properties and dependency injection lets you choose only the ones you need

@Froot I agree with you. It was more of a joke. Seems like these days I see it implemented everywhere for everything and just makes the code more complex and less readable for zero benefit. It has its place for sure, but recommending that someone use it without a defined purpose and goal is a waste. The recommendation I hear is "you should use DI because loose coupling is totes amazeballs" but no actual proof behind the statement and only contrived examples of where someone would swap out a database and suddenly everything is better because DI was there to save the day. No. I have never seen it used properly for that purpose and neither has it helped make that "easier refactoring" a reality.

@molynerd It seems that the whole tech scene is just a game of who can shout louder so I kind of agree with you there