At my first job out of college, there was a "utils" file with IIRC over 100k LoC. Nearly every file in the codebase imported it. This was in Perl. That single import statement would increase the time to start anything by upwards of three seconds. One of the best things I did for my efficiency was to factor out subsets of functionality that didn't need any of those utils, since those subsets would run unit tests in a tenth of a second instead of three to five seconds.
All of which is to say, by all means argue about whether colossal files are acceptable software engineering, sometimes that fight takes a back seat to "a double-digit percentage of the company's CPU and memory are wasted on parsing and loading this file in literally every new process".
All of which is to say, by all means argue about whether colossal files are acceptable software engineering, sometimes that fight takes a back seat to "a double-digit percentage of the company's CPU and memory are wasted on parsing and loading this file in literally every new process".