Admittedly, my experience with TFS is a bit limited, but what you are describing is not the same thing. In fact, it highlights one of the problems I was talking about: With SVN, because dealing with branches is more cumbersome, people use the working copy as the place where they do their work. The result is that you have no version management of the work you are doing until you commit to the central repository.
This is not how you work with Git. With Git, you commit often. Every commit is tiny; it's the smallest possible atom of work which can't be divided further in any meaningful way. Before I started using Git, there was a whole lot of commenting out lines back and forth, committing only a selection of the dirty files in my working copy, and all kinds of similar things which effectively amounts to a kind of error prone, small-scale revision management by hand. Now all this is handled by Git, and it does it much better. Every change can be traced, reordered, combined, split, and so on. So when I say that my topic branch is floating nicely on top of the master, I'm not talking about the stuff in my working copy, I'm talking about my local revision history.
Furthermore, what I'm saying is not that certain things are impossible to do with Subversion. I'm saying that the mechanics of those things are so different that it fundamentally changes how you think of an use revision control in practice. It took me a few months of intensive Git usage to realise that.