Hacker News new | past | comments | ask | show | jobs | submit login

Ability to structure your code base hierarchically

Ability to search through your codebase by file name

Ability to hide irrelevant information and expose a higher level API through private functions




None of those are necessarily driven by file-level organization, though, except for the one about the file names themselves.

My mortgage is paid by a 50 kLoC C program with a single 11000-line function. I'm always blown away by how many so-called "code editors" can't give me a simple list of C functions in the file, the way BRIEF could in 1987.

Few things annoy me more than having to trudge through a codebase with hundreds of .c files, inevitably all with 8-character filenames. Any day when I have to break out Eclipse to navigate an unfamiliar project is an official Bad Day At Work.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: