For a while I've been saying our stacks are outgrowing hierarchical file systems. Hierarchies force one trait to have more power than another, even though each

For a while I've been saying our stacks are outgrowing hierarchical file systems. Hierarchies force one trait to have more power than another, even though each may be very important at different times. There may still be inherent hierarchical patterns to the code, but that doesn't have to be our only view. Further, during compilation a file hierarchy may still be needed, but the IDE doesn't necessarily have to force that view during the normal course of dev work. It's mostly to make the compiler happy, not the developer. Related ideas: https://www.reddit.com/r/AskProgramming/comments/j6uivx/crud_frameworks_or_languages_that_are_flexible/ https://www.reddit.com/r/AskProgramming/comments/j6uivx/crud... I'm glad to see experiments along that line. I doubt anybody will get it right the first time, but technology often requires experimentation to make it practical. I just know that hierarchies are too constraining for non-trivial code bases. Typical CRUD stacks can be viewed as a big pile of event handlers. How all these events are listed, sorted, searched, filtered, etc. should be based on RDBMS or RDBMS-like tools to give as-needed views via queries and query-like interfaces, such as Query-By-Example.