[slx26]

There are many different criteria to decide where to put your code or how to group it. And each case benefits more from one idea or another (and each codebase contains many different cases). Humans don't organize knowledge in folders in their brains. The information network is much more complex. We can't find a good solution only with folders.

In fact, the idea of trying to model complex systems in a text format divided in files (most programming languages) doesn't quite hold... gracefully at least. For example, the frequent discussions about inheritance and generics are pretty revealing of the fact that we mix modelling and implementations in the same working space, when in fact in many cases it would be better to work on those at different layers.

So, in my opinion, to really make "code colocation" better you would kinda need to start modelling complex systems with richer toolsets that don't try to express them only with code files. You can't properly work with complex systems with a single view, no matter which one you pick.

[valenterry]

Totally agree. Files&Folders are almost omnipresent, which is why people get used to it so much that it starts to shape how they think about structuring things.

But if you take a step back, they are actually not the right abstraction for most things. In this case, a tagging system would serve the purpose much better.

Unfortunately, tooling that deals with files&folders and text is very mature and it will be hard to extend or even replace it.

[ChrisMarshallNY]

I tend to rely heavily on the storyboard, in my Apple development. It's going to be going away, with SwiftUI, and I'm not convinced that what SwiftUI provides will actually be a replacement, but we'll see how things shake out.