[surajrmal]

I work primarily in c++ and fully agree with the author. I think it makes more sense in the context of larger teams, possibly also monorepos. Review speed (both latency of feedback and how thorough your reviewers are), presubmit test runtime, flake rate, etc can lead to it taking a few days to get work submitted. In some cases you don't want to land work until you've finished a milestone of some sort. If others work on similar files to you, you will end up with several rounds of rebase conflicts to deal with too.

[ahepp]

Do stacked PRs do something to avoid rebase conflicts if two people touched the same file?

[surajrmal]

No but it's a lot simpler to rebase and address them with stacked commits.

[squirrellous]

I feel like parent was referring to a culture of shipping small changes frequently, which tends to result in stacked PRs.