Make your monorepo feel small with Git’s sparse index
This is well written and deserves my upvote, because sparse-checkout is part of git and knowing how it works is useful.That said, there's absolutely no reason to structure your code in a monorepo.Here's what I think GitHub is doing:1)  Encourage monorepo adoption2)  Build tooling for monorepos3)  Selling tooling to developers stranded in monoreposMicrosoft, which owns GitHub, created the microsoft/git fork linked in the article, and they explain their justification here: https://github.com/microsoft/git#why-is-this-fork-needed> Well, because Git is a distributed version control system, each Git repository has a copy of all files in the entire history. As large repositories, aka monorepos grow, Git can struggle to manage all that data. As Git commands like status and fetch get slower, developers stop waiting and start switching context. And context switches harm developer productivity.I believe that Google's brand is so big that it led to this mass cognitive dissonance, which is being exploited by GitHub.To be clear, here are the two ideas in conflict:*  Git is decentralized and fast, and Google famously doesn't use it.*  Companies want to use "industry standard" tech, and Google is the standard for success.Now apply those observations to a world where your engineers only use "git".The result is market demand to misuse git for monorepos, which Microsoft is pouring huge amounts of resources into enabling via GitHub.It makes great sense that GitHub wants to lean into this.  More centralization and being more reliant on GitHub's custom tooling is obviously better for GitHub.It just so happens that GitHub is building tools to enable monorepos, essentially normalizing their usage.Then GitHub can sell tools to deal with your enormous monorepo, because your traditional tools will feel slow and worse than GitHub's tools.In other words, GitHub is propping up the failed monorepo idea as a strategy to get people in the pipeline for things like CodeSpaces: https://github.com/features/codespacesBecause if you have 100 projects and they're all separate, you can do development locally for each and it's fast and sensible.  But if all your projects are in one repo, the tools grind to a halt, and suddenly you need to buy a solution that just works to meet your business goals.