A few years ago I was chatting with some fellow geeks, and, as often happens, we got on to ridiculing PHP developers. Ha ha! Every PHP app is one big file! Wha

A few years ago I was chatting with some fellow geeks, and, as often happens, we got on to ridiculing PHP developers. Ha ha! Every PHP app is one big file! What losers. Yeah, we were having blast with these digs. But then I realized that, at least in some ways, this was an epic win. Have to go dig into some alien app? No worries; everything you need (or probably care about) is in the one big file. Need to deploy? FTP that one big file. Seriously, maybe it's not as crazy as it seems. The better approach might be for your editor to behave as if all code were one big file, when needed, and behave as if all code were nicely split out, when needed. And have multiple files makes life easier when you're on a team and several people are touching different parts of an app. But before rejecting something like this out of hand, consider what your needs really are, and if how you're doing things is really what's going to work best for you.