Lots of things right, but tools shouldnt make you work their way.

I really wanted to love Cornerstone as a replacement for Versions that my team has been using for the last couple of years. On the surface Cornerstone is well done, it provides well thought out accesses to many of the basic features, and brings some interesting approaches to daily repository management. What Cornerstone gets wrong, however, causes more pain than its worth. I choose tools because they make my day-to-day life easier. They get out of the way and let me work the way I need to to be efficient. As it stands of this writing, Cornerstone requires to many forced compromises in workflow.

We work with large media asset based projects that for several reasons require the libraries of media to be in the repository. If you have ever had to rename, move, or delete 200+ plus assets in a working copy from within the IDE or the Finder youll understand. Cornerstone provides NO graceful way was dealing with this. Rather I when you want to commit your changes in Cornerstone I have had to manually command-click each and every file and mark them for deletion. Are you kidding me? If your assets are located across several folders this issue gets even worse. Deleting a folder from the Finder, then marking it for deletion has caused Cornerstone to fail to commit the changes to the child objects on several occasions. I emailed their support, and the answer I got was not to delete files or folders from outside of Cornerstone.

Conclusion:
These guys got a lot right in Cornerstone, and this is a solid application for many people. For our use case, it just forces to many compromises as it stands now.

iGoodtimes about Cornerstone