[erik_seaberg]

I've been the git fixer for a few different teams. I want to like submodules, but there's something that doesn't fit my brain the way the rest of git does. It feels half-baked. I think we're still missing the best way to model the problem as a tree of related states.

[Pxtl]

They feel like an unfinished tool provided by a third-party, not a built-in component of git.

The simple fact that switching branches doesn't auto update the submodule is awful.

[kasbah]

You can change that behavior now in newer versions of git:

    git config --global submodule.recurse true

https://stackoverflow.com/questions/1899792/why-is-git-submo...

[colechristensen]

Agreed. I also want to like submodules but every encounter with them has been an awkward confusing mess.

They're fine if they are completely hidden from human interaction and used in a programmatic way, but the human interface with the concept seems to always be so awkward.

[neolog]

Everything about git feels half-baked tbh

[spicybright]

I agree with a half baked UI. It feels like they kept on tacking on more and more commands and flags to get to where we are today. But the fundamental data structures the UI operates on are rock solid though. I'm actually surprised more software doesn't use git's internals for things besides version control.

[ChrisMarshallNY]

My understanding was that they were designed by someone that likes monorepos.