|
|
|
|
|
|
by reedlaw
4477 days ago
|
|
|
I feel much of the negative reaction to posts like these fails to grasp the main idea. My take is that you can use other architectural patterns than MVC and still benefit from Rails. In fact, you can use patterns that complement MVC. There is no conflict. Why ignore the history of design patterns and try to squeeze everything into an MVC-shaped box? |
|
|
I feel much of my negative reaction to this post and those like it -- and I am familiar with hexagon/ports-and-adapters architecture -- is failure to clearly present a main idea, or even to connect the dictates in the post to the subject in the headline.
> My take is that you can use other architectural patterns than MVC and still benefit from Rails.
Certainly, the article seems to be trying to use Rails MVC structure to force the design of the web-facing adapter in a hexagonal architecture into an MVC design, what it really fails to do is justify this as a good thing to do (either in general for building an application, or starting from the assumption that we should use a hexagonal architecture, or starting from the assumption that we should use Rails.)