Software reuse comes with the challenge of dependency bloat, which refers to unneeded and excessive code incorporated into a project through reused libraries
Our analysis is the first to focus on different granularity levels, including bloated dependencies, bloated files, and bloated methods.
I don’t have time to read this at the moment, but do they ever go into what “excessive code” is? All I see is the word “bloat” repeated a lot and think this is some kind of premature optimization that ultimately doesn’t matter.
we analyze the source code of 1,302 popular Python projects and their 3,232 transitive dependencies.
Out of the 36 submitted pull requests, developers accepted and merged 30, removing a total of 35 bloated dependencies.
It doesn’t sound like it had all that much of an effect either.
I don’t have time to read this at the moment, but do they ever go into what “excessive code” is? All I see is the word “bloat” repeated a lot and think this is some kind of premature optimization that ultimately doesn’t matter.
It doesn’t sound like it had all that much of an effect either.