3 ms·
"If it ever came time to switch payment gateway backends, in a Java application using DI you would just need to switch which implementation of your interface th
by jerf 16y ago
"If it ever came time to switch payment gateway backends, in a Java application using DI you would just need to switch which implementation of your interface that the rest of your code is wired up with (either in XML, or if you are wiring up collaborators explicitly in your code, etc)."
You simply pass in the desired payment processor as a parameter. End of story.
This is part of the reason Java is such a terrible language for actually learning about programming. "Using Dependency Injection" is an absurd way of phrasing "pass in varying parameters as parameters to your function instead of using global variables". What should be the normal way of doing business has instead been elevated to Something Special (that Lesser Languages Can't Do because they don't call it Dependency Injection because they would never think of giving Passing Parameters to Functions a special name!) because Java makes something as easy as breathing and in some cases hard to avoid (try programming Haskell or Erlang with too many global variables) a production.
In Java, you use absurd and unnecessary machinery. In every other language, you just do it. It's hard to even explain how you do it because there's hardly any doing in the it. It's a parameter passed in. It hardly seems worth discussion.
- brown9-2 16y agoFor the sake of this example, let's say that the different gateways have vastly different APIs, messaging mechanisms, etc. So in the code that you are passing a parameter to, you'd have to have some sort of branch based on the parameter value to choose to call Gateway A versus Gateway B - correct? Which requires you, when switching gateways, to change the value of the parameter passed along with possibly updating the branch to be aware of what the different Gateway modules you might call would be - correct?
- jerf 16y agoThis is basic object orientation: You pass in an object that corresponds to the desired interface. "Facade pattern" if you need something to Google, but this is really basic language-agnostic OO stuff. Another reason to dislike the Java cruft; it successfully hides the simple things going on behind immense machinery and complicated terminology.
- brown9-2 16y agoSo this is what confuses me about claims that in Python you don't need all this extra cruft, because the language makes these things possible: if you are using the Facade pattern in Python for this example, you'd be using the same pattern in Java. So then, what exactly is different here?
- deleted 16y ago[deleted]
- jerf 16y agoNothing! Dependency injection is just programming. You don't need a "framework" for it, even in Java. Java is crufty in other ways that may make various objects more painful to use than in Python; where you need a zoo of classes in Java you often don't in Python. But this isn't one of those places. The term does nothing but create confusion for no good reason.