Re^3: $class = ref($class) if ref($class) Redux (theory)

I can readily see what you mean when you say Moose is anti-modular. I would be more inclined to say that there are those who have taken modularity to an extreme with it and have lost sight of a project's architecture in the process.

Please could you give an example to clarify what you mean by this?

Comment on Re^3: $class = ref($class) if ref($class) Redux (theory)

Replies are listed 'Best First'.
Re^4: $class = ref($class) if ref($class) Redux (theory) by boftx (Deacon) on Jul 08, 2014 at 14:27 UTC
What immediately comes to mind was a case where modules used several Roles, each with a single method, in a way that would have been easily achieved with having the methods directly in the modules. The roles were not used by any other classes and did not implement any kind of API for the modules. It wasn't a case of just a single module that did this, but instead, this was a normal design practice. To me, that was needless complexity. You must always remember that the primary goal is to *drain the swamp* even when you are hip-deep in alligators.	[reply]

Replies are listed 'Best First'.

Re^4: $class = ref($class) if ref($class) Redux (theory)
by boftx (Deacon) on Jul 08, 2014 at 14:27 UTC

What immediately comes to mind was a case where modules used several Roles, each with a single method, in a way that would have been easily achieved with having the methods directly in the modules. The roles were not used by any other classes and did not implement any kind of API for the modules. It wasn't a case of just a single module that did this, but instead, this was a normal design practice.

To me, that was needless complexity.

You must always remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.

[reply]