This was one of the main problems with the first popular MVC web framework for Java: Struts1.

It’s hard to understate how popular Struts1 was in the Java community circa 2003.

Therefore, it grew rapidly and organically, and unfortunately this resulted in all roads leading to struts-config.xml.

The file could balloon to thousands of lines, especially if you wanted readable XML, and merge conflicts were a constant source of worry on larger projects.

Well with the minimum amount files resonates to me as that huge files of code that do not separate concerns and actions.

I am not really a fan of one file to handle all the actions one a resource, but this is often the case, but what pisses the heck of me is when the files goes to the thousands of lines and deals with many resources… it’s just a nightmare and a sink hole of our time

But probably the minimum amount of files you are referring to are not related with the code for the project itself?

^^ Sounds like a good topic for a thread

Rails championed a simple MVC structure which many frameworks also adopted. However I really liked Volt’s idea of building your app as a series of components. Something that bugs me is when I am working on something then have to jump to various folders. I know editors like Vim can make it easier but sometimes I just want to use the side panel file browser to get where I want to.