I mean sure but it turns this: - Checkout different branch - Continue working Into this: - Checkout branch into new location - (Close project in IDE) - Br

I mean sure but it turns this: - Checkout different branch - Continue working Into this: - Checkout branch into new location - (Close project in IDE) - Browse to branch location, open IDE - Move all terminal $PWDs to the new location, as needed - Make a coffee while the IDE re-indexes everything - (Compiled languages: Hit make, enjoy another coffee while the build runs) - (npm and similarly structured projects: Hit install, enjoy another coffee while all dependencies are being fetched/checked/installed) And I just don't see how that's desirable. With git I can create, merge and switch between branches in seconds, and don't really have any problems (I've almost never felt the need to have two branches checked out at the same time). But with tree-per-branch I only see problems, and all branch-related operations become slow and annoying. One use case I could imagine where this is useful if you are simultaneously maintaining several mainline branches. But even within those "work areas" I'd rather be able to quickly switch branches.