3 ms·
A colleague and I had a discussion about this particular author. The conclusion was that he's an older programmer that doesn't like when the technology changes/
by jdpanderson 12y ago
A colleague and I had a discussion about this particular author. The conclusion was that he's an older programmer that doesn't like when the technology changes/evolves. Anything new is EVIL, and sometimes the people evolving the technology get slandered in the process. This is visible in this and many of his other articles.
Edit: shouldn't have used the word "older". It has nothing to do with it. He's a programmer that doesn't like when technology changes/evolves.
- LoSboccacc 12y agoHe has a point. For most uses I see of DI, a service locator would have been better. I think that some framework got too far with DI, especially those where a dependency is managed in a file which cannot be debugged or overloaded (i.e. spring with xml). As long as DI is used to decouple services, that's seems fine to me. Decoupling object in the dm hover seems overkill - like in the sample, where the address is injected on the person class. That rarely makes sense
- aikah 12y ago> he's an older programmer I don't think that has anything to do with age. Adaptation or Learning might be harder as you get old, yet you can find as much young developers that stick with things they know and refuse to learn or use new stuff. The whole "no framework" movement for instance in front-end development, "because frameworks are too complex". I doubt older developers prefer writing everything from scratch because framework X or Y requires reading the docs. Everybody has opinions on things, even younger developers write "rants" like that.