I have to stop this in the first place, but:
Rebuilding something that already exists as a plugin or module.

Why the fuck should I make everything from zero if there's already something working that suits all of my needs?

On the other hand, avoid abusing the usage of plugins in order to avoid demolishing performance

my reason would be either I have a different usage of that specific function on a repo and I don't want to include all of that other things as a bloatware, or I am just too lazy to check if that repo *is* actually the thing I am looking for.

@melezorus34 yeah, plugins should have really less features, in order to be lighter
bc there's no way one actually uses ALL of one plugin features

@ZioCain by making a suite is small plugins that have distributed their features instead of one big plugin that is a get-one-have-it-all mentality.

I like that approach you're saying. If you want all, just use all the suite of all the small plugins.
But they might not want to charge you money only for 10% of their plugin but for the whole of it. They might also be lazy

@lostinmyworld *points to the meta-packages (usually end with ".common" or ".core") where they install all the plugins of that plugin tree*

An example is LibreOffice.common in apt