Timeline for Dependency Injection: What are advantages of using a framework?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2021 at 10:04 | comment | added | Walfrat | quite some library have pure code and have a spring integration. This keep it more flexible but there is also an extra cost to make it separate. It does make sense for a library tbh. But for me, considering that I would move from Spring while staying in Java make little sense. I could move to NoSQL, from a Web client to a Desktop Client, but I see extreme little reason to consider that I woulc move from the framework I use. I could ofc take the time to separate like a library, but i'd have a hard time explaining justify that cost to non technicla people that hold the money. | |
| Mar 17, 2021 at 9:55 | comment | added | candied_orange | @walfrat the less the code knows about the framework the more flexible the code is. It used to be that spreading knowledge of a design decision everywhere was only acceptable when the decision was choice of programing language. When you do the same with a framework you're effectively inventing a new language to work in. That comes at a cost. | |
| Mar 17, 2021 at 9:22 | history | edited | Walfrat | CC BY-SA 4.0 |
added 168 characters in body
|
| Mar 17, 2021 at 9:19 | comment | added | Walfrat | @candied_orange it's about "standarsing" (making standard ?) your architecture and code. It has a lot of advantage and ofc some inconvenient, like the learning curve which is a bit harder than just the langage. How can a framework be a framework if it doesn't "standardize" the architecture/code it covers ? | |
| Mar 17, 2021 at 9:16 | comment | added | Walfrat | @RobertHarvey the downsides of singleton when they're not done with DI container is the hard dependencies and hard call to "MyServiceImpl.getInstance()", since the DI do it for you without needing to have direct dependencies, you do not have that downside of the Singleton pattern. | |
| Mar 16, 2021 at 23:30 | comment | added | candied_orange | @Fabio their goal seems to be to trick you into using what is effectively a new language. One that specializes in something called vender lock in. I mean, they don’t force you down that path. But they make it awfully easy. | |
| Mar 16, 2021 at 18:02 | comment | added | Fabio | This is nice example when framework trying to do too much for you :(. Talking about transactional annotation | |
| Mar 16, 2021 at 17:10 | comment | added | candied_orange | @RobertHarvey yeah but I’ll never forgive them for cluttering POJOs with annotations. | |
| Mar 16, 2021 at 15:41 | comment | added | Robert Harvey | I find it fascinating that we've immortalized the Singleton (widely regarded as an anti-pattern) in DI containers, but I agree that having the ability to specify lifetime scope is a very useful feature. | |
| Mar 16, 2021 at 15:35 | history | answered | Walfrat | CC BY-SA 4.0 |