2 ms·
This is a problem mainly for people who use GUIs. When you use a terminal you don't really care how many files are in a directory, unless they have names that
by chmod775 6y ago
This is a problem mainly for people who use GUIs.
When you use a terminal you don't really care how many files are in a directory, unless they have names that are annoying to autocomplete.
- epistasis 6y agoIf that were the case, why would we bother separating out code into multiple directories at all? The reason we bother with modules and directories is to help organize code and ease discovery. And whether we use ls or a GUI, we all start out the process of discovery with a directory listing. The top-level directory, where these files are, is often where there's the most flexibility in terms of how to lay out things. All this clutter hides the project organization and makes it difficult to discover what's going on. It was one thing when it was just autotools, but the proliferation of tools in the last decade has brought it over a tipping point, IMHO.
- chmod775 6y ago>If that were the case It is the case: They don't bother me when I'm using a CLI, but when I use Visual Studio Code for instance, all those files are annoying when I'm looking for something/scrolling past them.