undefined | Better HN

0 pointstail_exchange2y ago0 comments

You must be really lucky then. In my previous job, inheritance and abstract classes were everywhere. Coupled with dependency injection frameworks that "worked like magic", it was really hard to follow the code inside that big, monolithic app. It made me never want to work with Java ever again.

0 comments

bb882y ago

I've never been a big fan of dependency injection. It solves a problem with unit testing in Java, sure, but the reality is that Java could have done some nifty things to help alleviate that as well.

jhaenchen2y ago

Agreed. Java injection frameworks are opaque and accomplish what they need to with overly powerful mechanisms because of the nature of the language. You don't see that sort of nonsense in python.

kaba02y ago

Wtf, so what do you think Django is?

1 more reply

za3faran2y ago

Nothing to do with the nature of the language, but with the nature of the program.

If you're writing a few line script, you don't need a DI container. Once your program gets large, it becomes extremely messy without one. It's no surprise projects like [1] exist.

[1] https://github.com/ets-labs/python-dependency-injector

1 more reply

baka3672y ago

If that’s the only thing it’s used for in the project, then you are most likely good with Autowired (in Sping) or something similar.

Any complicated DI solution must have a reason for it being there and I’ve seen too many projects complicating themselves on buzzwords like DI or MSOA without really needing either that much

throwaway29902y ago

Sounds like you’re confusing DI with DI containers.

winrid2y ago

I've seen the same craziness with NodeJS, and very simple Java services with minimal inheritance.

j / k navigate · click thread line to collapse

0 comments

bb882y ago

I've never been a big fan of dependency injection. It solves a problem with unit testing in Java, sure, but the reality is that Java could have done some nifty things to help alleviate that as well.

jhaenchen2y ago

Agreed. Java injection frameworks are opaque and accomplish what they need to with overly powerful mechanisms because of the nature of the language. You don't see that sort of nonsense in python.

kaba02y ago

Wtf, so what do you think Django is?

1 more reply

za3faran2y ago

Nothing to do with the nature of the language, but with the nature of the program.

If you're writing a few line script, you don't need a DI container. Once your program gets large, it becomes extremely messy without one. It's no surprise projects like [1] exist.

[1] https://github.com/ets-labs/python-dependency-injector

1 more reply

baka3672y ago

If that’s the only thing it’s used for in the project, then you are most likely good with Autowired (in Sping) or something similar.

Any complicated DI solution must have a reason for it being there and I’ve seen too many projects complicating themselves on buzzwords like DI or MSOA without really needing either that much

throwaway29902y ago

Sounds like you’re confusing DI with DI containers.

winrid2y ago

I've seen the same craziness with NodeJS, and very simple Java services with minimal inheritance.

j / k navigate · click thread line to collapse