> I've seen the simple act of untangling a globbed dependency to the various isolated files reduce the size of an output artifact by gigabytes. And I don't tak

> I've seen the simple act of untangling a globbed dependency to the various isolated files reduce the size of an output artifact by gigabytes. And I don't take issue with what are obviously exceptional cases. What you are describing is not "I put togeather 5 related files" it's like "I globbed a file I wasn't supposed to". > You're calling literally every language that doesn't use the c-linker an immature language. Which may include c++17-with-modules, though I don't know that for certain. Uhhhh, I don't think you understand how the feature in question functions. I am simply talking about the -M option family of gcc (and similar commands for other compilers). Which provides a dependency tree for C++ files. > At least not if you do any fancy precompilation/tree-shaking to your js at compile time. I think it's actually the opposite. Those are the same tools that provide the reflection features in question (or some other AST parsing library)... then you write a two line lambda and feed that in over an interpreter. Boom list of files.