4 ms·
The OP complains that: > For most programming tasks, editing involves opening several files at once and switching between them (e.g. HTML/JavaScript/CSS). His
by breck 17y ago
The OP complains that:
> For most programming tasks, editing involves opening several files at once and switching between them (e.g. HTML/JavaScript/CSS).
His idea of a solution is for better file navigation.
My claim is that often the real problem is a bloated set of files and directories in a project.
I find when the set of files is small, opening and switching between them is much faster and more productive.
This applies particularly to the beginning of a project. As classes/files mature, then I recommend splitting them up into more files.
For example, when starting a new MVC project I'll create one models file. All the models go in there at first because the project will be heavily edited.
Once it's become more stable, I'll split it into a file for each model/class.
This way when you make small changes you'll have the VCS history benefit you mention, but often you don't really need that at the beginning of a project.