By strictly, I think most developers mean one SCM tool's functionality is a strict superset of another's. That is not the case with git and svn! Git is probably qualitatively better for most competent developers, but for strictly, every feature counts -- git's support for handling binary files, in terms of size and content, is not as complete as svn's; and tree tracking is just completely different.

This means some developers will want things that svn can do but git can't. I don't think it's fair to deny that these gaps exist when some projects depend on it.