It presented an argument, offered alternative viewpoints, and articulated why the author thinks his approach is better than alternatives (without overly attacking them). Code samples were provided with real-life examples.
Whether or not I side with Concerns or DCI or something else, I got value out of reading this post and my understanding of Concerns improved.
This is a welcome relief to what was becoming a tense and drama-filled debate (Rails OOP design). Nice work, dhh.
If you want more, just check out the tweets between @dhh, @garybernhardt, and friends on Twitter yesterday. There are also links in there to blog posts and code examples using DCI, DAO, etc. to achieve similar goals.
It presented an argument, offered alternative viewpoints, and articulated why the author thinks his approach is better than alternatives (without overly attacking them). Code samples were provided with real-life examples.
Whether or not I side with Concerns or DCI or something else, I got value out of reading this post and my understanding of Concerns improved.
This is a welcome relief to what was becoming a tense and drama-filled debate (Rails OOP design). Nice work, dhh.