Re: Is IoC containers harmful for DDD?

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.

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

>
>
> On Mon, 01 Dec 2014 07:53:07 +0100
> "Thomas Presthus [email protected] [domaindrivendesign]"
> <[email protected]> wrote:
>
> > magic. You should check out Greg Youngs keynote "8 lines of code"
> > here: http://www.infoq.com/presentations/8-lines-code-refactoring
>
> Interesting talk...
> While one can't disagree with the examples he provides, I really hated
> the examples.
>
> AOP is magic and yeah, you should avoid it unless you need it.
> And you need it only when you can't/won't change the code - meaning you
> can't/won't compile it, but you want to change the behavior.
> This goes along his point that you should be careful about the
> dependencies you take in, but if you don't want to reinvent the wheel
> all the time, you'll have plenty of external dependencies.
>
> I really hated the snark remark about MDA, since the same argument can
> be applied to the compilers, databases, OS and every layer underneath
> it. As someone who is doing MDA I guess I took it personally :D
>
> All in all, good talk... more devs should see it. Even if I
> disagree with some of his conclusions and dislike a lot of premises.
>
> Regards,
> Rikard
>
> --
> Rikard Pavelic
> https://dsl-platform.com/
> http://templater.info/
>  
>



-- 
Studying for the Turing test