Re: Is IoC containers harmful for DDD?

No disagreement there.
What I didn't like is that takeaway is - AOP is bad... don't use it.
If you stated let's take a look at some of often, yet bad usage of AOP
I would not have any issues with that part of the talk ;)

AOP is not inherently bad though the too-much-magic aspect is common. The
way most people are using it is just ridiculous.

I would still have issues with the bootstrap method, but thats
whole other discussion (and goes against some of the DDD values).

I'd love to hear which DDD values it goes against.

On Tue, Dec 2, 2014 at 2:37 AM, Rikard Pavelic [email protected]
[domaindrivendesign] <[email protected]> wrote:

>
>
> On Tue, 2 Dec 2014 02:15:20 -0800
> "Greg Young [email protected] [domaindrivendesign]"
> <[email protected]> wrote:
>
> > Functional composition can remove many places AOP is needed. As
> > example in most domain models people are applying interception at
> > application service level, here functional composition is a much
> > simpler and cleaner way of handling things.
> >
>
> No disagreement there.
> What I didn't like is that takeaway is - AOP is bad... don't use it.
> If you stated let's take a look at some of often, yet bad usage of AOP
> I would not have any issues with that part of the talk ;)
>
> I would still have issues with the bootstrap method, but thats
> whole other discussion (and goes against some of the DDD values).
>
> Regards,
> Rikard
>
> --
> Rikard Pavelic
> https://dsl-platform.com/
> http://templater.info/
>  
>



-- 
Studying for the Turing test