chihuamaranian<p>I'm working with a team that does not like <a href="https://tech.lgbt/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dotnet</span></a> <a href="https://tech.lgbt/tags/nuget" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nuget</span></a> packages. </p><p>They would prefer nothing, but if forced into reusable modules they would choose git submodules first. </p><p>This is surprising to me, but one of the reasons listed holds weight: with git submodules you can hack, modify, and change the modular code inline. No review, build, & publish pipeline to try out a idea. </p><p>I am trying to deduplicate a lot of copy and paste "mostly the same" code, and firm up the abstractions and interfaces of these modules (there's a rant in there for a different time)</p><p>I'd like some more opinions on the nuget vs git submodule topic. Git intuitively seems like the wrong package management tool to me, but I don't know if I'm holding on out of stubbornness or if there is something on the tip of my tongue I just can't articulate yet. </p><p><a href="https://tech.lgbt/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a></p>