+972 52-548-6969
Why I don't like the Team System SCM
time to read 1 min | 135 words
Mahor reason: Latency.
On a local network, it takes more than 0.2 second (the human noticable delay) to checkout a file. This means that I can open a file, start editting it, and for a split second, not get a response from the editor. Annoying as hell.
Jeffrey Palermo posted about a refactoring he had made that touched 200 files. Using the Team System Model, that is nearly a minute when the IDE is basically unusable. I tend to do this kind of refactoring fairly often, and it feels like I am back using the VS Refacoring support.
Minor reasons: poor support fo disconnected scenarios, read-only files, the cmd line tools will throw up a GUI interface, no lightweight client support.
Comments
My number one Ho Snap! Is that it does not store the file times. It only stores times for the Changeset creation. This means that when you do a get of any kind the timestamp in the files gotten is always now!
Thanks for the trackback, but I'm Jeffrey Palermo, not Jeremy Miller. :-)
Opps!
Sorry for that, fixed.
Yeah, I'm stuck using TFS every day during my "day job" and that delay is really just the nature of the whole check out/in model of SCM. Shelvesets can be useful, but everything else about TFS is for the birds...
Thank goodness I have edit-merge-commit with Subversion to keep my sanity for all of my side and personal projects.
Comment preview