I'm a junior dev and at work the senior dev that essentially mentors me into not being useless at the job heavily discourages adding a System.Net.Http dependency to a project within the solution as much as can be reasonably gotten away with.
From what I remember one of the issues with it is that it's supposed to be a really fat dependency to introduce to a project, but I'm wondering if from a package size aspect that matters much nowadays other than slowing down the speed of a deployment and fattening the binary?
Does that even matter if the dependency would be added to a library project within a solution that already has references to the dependency?
Outside of the context I described, are there other reasons to avoid packages such as System.Net.Http or any other ones that could perhaps in some way be notorious?