svn - What are the advantages/disadvantages of Git's snapshot-based approach in practice compared to the traditional VCSs? -

in official git book can read this:

git thinks data more stream of snapshots. important distinction between git , other vcss. makes git reconsider every aspect of version control other systems copied previous generation. makes git more mini filesystem incredibly powerful tools built on top of it, rather vcs. we’ll explore of benefits gain thinking of data way when cover git branching in git branching.

what difference make in practice? in book says benefits covered in branching topic not mentioned there , not see why important. example can create branches in svn, can create patches (like cherry picking) , on. why snapshot behavior useful compared svn?

note git , have no intention of bashing wish understand better.

one of main advantages remains in term of merging, domain svn struggles @ time.
(see "how and/or why merging in git better in svn?")

you combine graph of commits (dag) representing branches (instead of svn subtrees) , snapshot representation associated each commit:

from pro git book:

git simple three-way merge, using 2 snapshots pointed branch tips , common ancestor of two.

instead of moving branch pointer forward, git creates new snapshot results three-way merge , automatically creates new commit points it. referred merge commit, , special in has more 1 parent.