TFS has some redeeming qualities when looked at as part of a holistic software development platform - bug tracking, work items ect. but purely as a source control system it is bad.
Day to day experience is just friction, friction, friction.
And guess what keeping source control and your IDE seperate is actually a good idea. Also why do I care that Alex down the hall has opened a file - what am I supposed to do with that information...
"And guess what keeping source control and your IDE seperate is actually a good idea. "
Too true. Killing time watching your IDE lock up is not fun. Nor is the fact that _some_ IT departments still haven't performed the upgrade from TFS 2005 unservicepacked
"The offer was simple: Pay Microsoft a $50,000 fee plus a share of any revenue, and in return it would provide this great platform for publishing, with proprietary publishing tools and file formats that would restrict our content to users of the Microsoft platform."
Downside - you probably wouldn't have a business right now.
Good choice from Tim - I wonder how long he considered it for?
I'm afraid the web might come full circle back to something like we started with separate networks and walled off content. The recent buzz about Cable companies wanting to restrict online content to paid customers and the net neutrality flap are examples of this. As belts tighten content owners are getting scared and want to monetize their 'stuff' with more control.
As a caveat, if you are thinking of buying a voice like Lucy, it does not work with Windows' built-in Text-to-speech (for example - Adobe Reader's text-to-speech feature). It looks like Lernout & Hauspie has some kind of agreement with Microsoft to lock out other competitors.
Day to day experience is just friction, friction, friction.
And guess what keeping source control and your IDE seperate is actually a good idea. Also why do I care that Alex down the hall has opened a file - what am I supposed to do with that information...