What do you like best?
Tracks a whole commit which makes it easier for a developer to keep track/check the history.
Overall revision number makes build versioning and regression testing much easier:
Prevents accidental committing of conflicted files.
Offline diffs and availability of customs diff's.
supports versioning of binary files
What do you dislike?
working copies take up twice as much space.
recursive greps of source directories now turn up lots of bogus hits in ".svn" subdirectories
Need to forcefully commit executable files/binary files.
SVN will now not automatically cope once you've removed the conflict markers from a file. It will have marked the file as "conflicted" when it first displayed the C status, and when you've sorted it out you have to manually tell it "resolved".
SVN does not allow rollback of commit. Authors suggest copy good repository state to the end of trunk to overwrite bad commit. However bad commit itself will remain in repository.
Recommendations to others considering the product
SVN in Linux is far better than tortoise SVN available in Windows since we have to write down commands to commit the code it shows some more importance of what we try to do. I suggest people should double check before committing the code.
What business problems are you solving with the product? What benefits have you realized?
Mainly used for version controlling and code sharing.