4 ms·
> Rather than trying to figure out which of dozens of files has what you're looking for, you can just search one or two large ones. Why is this a good thing? T
by bigyikes 6y ago
> Rather than trying to figure out which of dozens of files has what you're looking for, you can just search one or two large ones.
Why is this a good thing? The same amount of code and same number of results need to be scanned either way. With many files, you at least have the file name to give you some small amount of context without needing to read the code.
- coder4life 6y agoWorking with 1 or 2 large files is vasty more productive/faster (for me) than working with 50 Seeing as Bellard is very prolific and has done more than you me and three others in a lifetime, there must be some merit to his approach.
- forty 6y agoExactly, I think it's trading write efficiency for readability. It's good for write only projects (so mostly personal projects I'd think)
- derangedHorse 6y agoAlthough I agree with the fact it was easier/faster for him, don’t fall into the fallacy of him being productive meaning he was efficiently productive
- andykx 6y agoYeah. This seems like something that the industry decided was a bad practice many years ago. My best guess is that this is more of a fun project than anything and spending too much time on such concerns would detract from the fun. I do the same with my side projects.