ClearCase SUXXX !!!

Тема говорит за себя (кто не в теме - тому неинтересно) Собственно, вот что говорится на википедии про этот кошмар разработчика (далее по тексту - КаКашка, от аббревиатуры): - Transactions not atomic: Changes to files or directories are independent from others, unlike some other systems where multiple changes can be committed atomically at the same time, using the concept known as Atomic commit. Atomicity is desirable because it allows multiple changes that address a particular problem to be committed as a single unit, and, provided the developer has been careful, results in a buildable code base for every version. - Aging: ClearCase itself, and tools related to it like ClearQuest, have stagnated and accumulated significant quantities of legacy code. This makes them slower and more difficult to use than other systems. ClearCase was designed to support existing build systems rather than require the developer to use only ClearCase tools such as clearmake. These included Makefiles, shell scripts, etc. - Speed: ClearCase dynamic views are slower than local filesystems, even with good network infrastructure. A benchmark shows that many basic tasks take about twice as long to run using a ClearCase dynamic view than on competing SCM tools, although repeated subsequent builds may run dramatically faster due to build avoidance if ClearCase's make substitute can be used. Because MVFS requires server access every time a file is accessed, the performance of the file system depends on server capacity. - Speed - Windows clients: ClearCase disk access performance for Windows clients are extremely low.This depends on unlucky combination of a very verbose protocol combined with Samba and CIFS. Replacing the windows clients standard CIFS implementation with NFS might increase the bandwidth approx. 2.5 times, leaving it still slow but more acceptable. - Sensitivity to network problems: Because MVFS is essentially an online file system, any problems with the server or network render the dynamic views unusable. It is not possible to work on dynamic views offline.[citation needed]. If the view data for dynamic views is stored on a client host (as may be done for performance reasons or to reduce the need for servers), ClearCase does not automatically handle host IP address changes.