Earlier quoted context omitted.
That might work if you have a very small app (example: HN, Reddit, Twitter web client etc) Imagine, on the other hand, large-ish web app (example: Salesforce, Netsuite). 300 tables in the database. Perhaps 50 of those can be manipulated directly from the menu. Customers, Purchase orders, Quotes, Reports, plus all the supporting stuff like Countries, States, Currencies and so on and so forth. Each of those need at lea…
> Each of those need at least CRUD, plus printing, paging, searching -- are you really going to copy-paste that 50 times? In MVC terms, that's either (a) the M, or (b) the C. Not the V. I suggested not trying to fight the (hidden) behavior in a superclass when working on the V layer. I stand by that. I've also advised some extremely large projects (over 5000 unique screens). My advice scales really well. You can do w…
Wait, what? How is the user supposed to invoke CRUD ops or printing or searching without a V? I don't think we are talking about same things at all.
In fact all of these operation span M, V and C. It's not anything new either it has been around at least since Smalltak (in current terminology).