问塑料SCM和汞？Windows 7下Visual 2005的源代码控制需求

EN

- Easy to use tools: from the GUI, the ShellExtension, Visual Studio Plugin, integrated diff/merge (yes! give a try to our [XDiff/XMerge with code refactor support!](http://codicesoftware.blogspot.com/2010/07/move-support-in-diff.html)), the Branch Explorer that basically let's you do all branching and merging from a graphical perspective... Ok, with Plastic you not only get the "engine", you get the entire car with all the pieces you need. I can mention other tools for VS users like the [method history support](http://codicesoftware.blogspot.com/2010/12/announcing-method-history.html), and the list grows and grows...
- Like Mercurial: totally designed to handle branching and merging. From my point of view (biased) branching is simpler in Plastic since "named branches" are there by default. We propose users to embrace ["branch per task"](http://www.plasticscm.com/infocenter/quick-start/intro-task-driven-development.aspx).
- Configurable database backends: you can store your data (and later use standard SQL interfaces if you need to build your own apps around) in SQL Server, Firebird, Oracle, MySql or even a tiny SQLite. We didn't reinvent the wheel here: transactional by default ;)
- ACL based security: probably not key for a small team, but it is there.
- For advanced mergers: each "changeset" in Hg is restricted to maximum two parents, you don't have this limitation in Plastic, but ok, we could argue about the details for hours... maybe not worth ;)
- Also for advanced integrators: we do handle merge tracking at the item level which means we can do "partial merges" (merge only part of a branch) seamlessly. It is a little bit harder with Hg and Git.

- DVCS is good not only because it enables distributed development, is good because all new DVCS systems (Hg, Git, Bazaar, Plastic...) **implement merge tracking right**. So, at the end of the day for many people DVCS is just about merge tracking done right (less shocking than pushing/pulling but true).
- Being able to have your own SCM on your laptop is simply great. I've been working with Plastic this way (now I have a SQLite based server, super-fast and super-light) for years and... well, is simply better: you never get slowed down by the internet connection, you can merge whenever you want (remember **branch per task**), review your own changes... everything. And then push your changes back to the main server when you're done. It is simply better.
- Now: Plastic SCM, unlike Git and Hg, is able to work in the two modes. Do you want to have a central server and directly connect to it without intermediate replicas? You can do it. Do you want to work in true DVCS style? You can do it too. That's why Plastic is so flexible.