3 ms·
Apart from being verbose, why is that a bad thing? Spring is used to successfully build massive applications. You can meme about Spring's AbstractFactoryBeans a
by royjacobs 7y ago
Apart from being verbose, why is that a bad thing? Spring is used to successfully build massive applications. You can meme about Spring's AbstractFactoryBeans all day, but in the end it does what it's supposed to do.
- p2t2p 7y agoRecently I had to hide a bunch of functionality for certain license type in a product. Spring + AspectJ turned it into a enjoyable experience - just add one annotation, two classes, one for aspect, another for exception mapper in rest and you can mark any class as "requires certain type of license" in one like of code now.
- scotchbonnet 7y agoI maintain a class library that is highly depended upon in the rest of our company. I don't like to introduce dependencies at my later because of that. So things like DI are all factory patterns / builder patterns. It's explicit and has kept my object lifecycle super manageable. It feels like the people who meme about EnterpriseFactoryFactory at times just haven't hit the right use case for it.
- RhodesianHunter 7y agoAnd if they do ever hit it, having never seen a reason to use it before, they instead layer over it with poorly thought out abstractions leading to unmaintainable code that they'll probably hoist onto the next dev.
- porker 7y agoI'd like to understand this more, as being on the fringe of popular open source projects I think I experience this. Can you expand any further with pseudocode?
- merb 7y agothe problem in angular is that it's bloated. and their components generate a load of bloat. Since basically all components have a FactoryComponent thingy, which you don't see, because it gets generated. However a bigger application can easily grow to a few mbs which is a huge no-no for javascript in the browser.