Here are the most common bits of FUD about svk.
- svk is built on top of Subversion, isn't it over-engineered and fragile?
First of all, svk only makes use of the 2 underlying layers of Subversion, which are considered solid, as it's the base of the popular system.
Secondly, fragileness is probably something subversion had before 1.0. It's rather robust now, at least speaking of its storage filesystem (libsvn_fs) of which svk makes heavy use. The remaining over-engineered part in Subversion is probably the working-copy management code (libsvn_wc), which svk doesn't use at all. In fact one of the reasons that svk was invented was to work around that nasty spaghetti code.
/Note, 11-11-05: Spaghetti code can certainly not be called over-engineered./
/2006-05-10: But it is often fragile, and that's the important bit./
Lastly, to be fair, Subversion is a very popular system, lots of people will be improving it, or at least keep the underlying filesystem sound and improved. So svk will benefit from the care-takers of Subversion.