Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Agree entirely with the article.

TFS is one of those products that you feel like you should be using what with being an ENTERPRISE, but after a couple of stand-offs with it, you feel like you've been thoroughly well and truly raped by the vendor. This is unless you were using VSS before at which point you are scarred for life.

I made a fair bit of cash between '03-'07 saving people from botched, painful VSS and TFS environments. If people pay you lots of money and worship the ground you walk on for getting rid of TFS, then it's probably a bad product.

I replaced them with a simple scripted virtual Debian/Trac/SVN appliance with Active Directory integration via LDAP. I let them design and build their own processes and workflows with Trac workflow. I do the same but with Trac and Mercurial now.



TFS is a below average source control system in an age when there are many better choices. VSS, on the other hand, is an active threat to all of your code.

At a previous employer, I was delighted by the switch to TFS, because it meant we no longer had to worry about the VSS file store getting corrupted and losing data. Now I'm on contract with another employer still using VSS, and we should be cutting over to TFS soon. Once again, I will be delighted. Because the below average is a welcome change from the flatly unacceptable.


Agree. I illustrated VSS to someone once by printing the source out and throwing it in the bin. That got the point through.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: