I ask myself "What does the each patten make easy? What does each pattern make difficult?" The standard or "verb-oriented" organization makes it easy to manage cross-cutting concerns, like rewriting all of your views in HAML instead of in erb, or adding a "created_at column to every model table. The refactored, or "noun-oriented" organization makes it easy to manage model concerns, like adding a new controller action with its associated views, model changes, tests, and migrations.
I find the latter happens far more often than the former for me, so it feels like a win even if I have no interest in sharing a model between applications.
Perhaps both schemes could be supported, using a system of symbolic links, or in its most elite case maybe even a specialized user-space filesystem. Now you have me thinking...
That's a classic matrix problem. Information fits nicely in two categories. How do you organize it? Choosing one or the other is mostly arbitrary. But current file systems force you to make a choice. BeOS a long time ago sort of wanted to fix that...
I find the latter happens far more often than the former for me, so it feels like a win even if I have no interest in sharing a model between applications.