I think for a lot of people the Model is the DB layer. They then (rightfully) realize that you shouldn't combine business and DB logic, and then move their busi

I think for a lot of people the Model is the DB layer. They then (rightfully) realize that you shouldn't combine business and DB logic, and then move their business logic into the Controller. So they're fixing a valid issue with an invalid solution, causing bloated and dual purpose (business and application logic) Controllers.