2 ms·
Agreed. Stuff like this feels like magic for magic’s sake, and as someone who has had to operate services that use these DI frameworks, they are a big pain.
by throwaway894345 5y ago
Agreed. Stuff like this feels like magic for magic’s sake, and as someone who has had to operate services that use these DI frameworks, they are a big pain.
- throwaway1492 5y agoWhat does “operate” mean in this context? I’m generally curious why one should consider this comment to be anything other than low effort flame bait?
- throwaway894345 5y agoOperate means “run the service”. If you need to configure things which aren’t well documented, it’s nice to be able to look at the code, but the DI frameworks obscure the code path. This is pretty straightforward; no idea why this would seem like flame bait—I didn’t even realize this was something people held deep emotional attachments to.
- kaba0 5y agoHow about learning about the tools you use beforehand? You don’t sit into a car without any knowledge about it and blame it that it is magical.
- deleted 5y ago[deleted]
- throwaway894345 5y agoI read all of the documentation for the service that I operate--per my other comment (https://news.ycombinator.com/item?id=29973282 https://news.ycombinator.com/item?id=29973282), often times things aren't well-documented and it's crucial to be able to look at the source code to figure out what something does (e.g., how is a configuration parameter used? what are its valid permutations?); however, when the source code is obscured by gratuitous complexity then it imposes a high cost on the user and in the case of DI frameworks, that gratuitous complexity comes with no discernible benefit (a car offers me something of value to justify its learning curve). Personally I'm of the opinion that a person shouldn't have to be a seasoned Java developer to use so many tools that are implemented in Java (or any other language, for that matter).