VCS 适合设计师使用吗？
我知道，毫无疑问，版本控制系统对于开发人员提高生产力和保护代码绝对至关重要。但是设计师如何使用 Photoshop（尽管它不特定于任何工具，只是为了让我的观点更清楚）。
VCS 使用增量压缩来存储不同版本的文件。这对于代码来说非常有效，但对于图像来说，这是一个问题。光栅图像文件是二进制格式，但矢量图像文件是文本（我想到的是 SVG）并且会带来问题。问题来自 .psd 文件（以及任何其他图像“源”文件） - 这些文件可能会变得相当大，并且由于我不熟悉该格式，因此我将它们视为二进制文件。在这种情况下，VCS 将如何工作？
如果 VCS 服务器无法有效地比较文件（或者更糟，根本不能），那么存储库可能会非常大，并且随着时间的推移，当有人需要检查存储库（或克隆它）时，这可能会变得非常痛苦如果使用 DVCS）。
你们中有人为此目的使用过 VCS 吗？效果如何？我对 Mercurial 最感兴趣，尽管这是适用于任何 VCS 的一般情况。
I know that a VCS is absolutely critical for a developer to increase productivity and protect the code, no doubts about it. But what about a designer, using say, Photoshop (though it's not specific to any tools, just to make my point clearer).
VCSs uses delta compression to store different versions of files. This works very well for code, but for images, that's a problem. Raster image files are binary formats, though vector image files are text (SVG comes to my mind) and pose to problem. The problem comes with .psd files (and any other image "source" file) - those can get pretty big and since I'm not familiar with the format, I'll consider them as binary files. How would a VCS work in this condition?
The repository could be pretty darned big if the VCS server isn't able to diff the files efficiently (or worse, not at all) and over time this can become a really big pain when someone needs to check out the repository (or clone it if using a DVCS).
Have any of you used a VCS for this purpose? How well does it work? I'm mostly interested in Mercurial, though this is a general situation that applies to any VCS.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
设计人员通常使用专门的工具，例如 AlienBrain、Adobe VersionCue 或类似的，本质上是理解图像和其他媒体资产的版本控制系统，它允许比较两个图像之类的东西。
恕我直言，设计师绝对应该使用 VCS 系统，至少作为版本控制和备份的一种手段 - 它们的内容与规范、文档、代码、部署脚本以及构成项目的其他所有内容一样重要。
我不知道前面提到的“资产管理系统”和 Developer VCS 系统之间是否存在桥梁。
Designers usually use specialized tools like AlienBrain, Adobe VersionCue or similar, which are essentically Version Control Systems that understand Images and other Media Assets, which allows stuff like diffing two images.
Designers IMHO should definitely use VCS systems, at least as a means for Versioning and backup - their stuff is just as important as Specs, Documentation, Code, Deploy Scripts and everything else that makes a project.
I do not know if there are bridges between "Asset Management Systems" like the mentioned ones and Developer VCS' systems though.
版本控制系统对于任何正在从事稍后可能需要旧版本的工作的人来说都是有用的。也就是说，我已经用 Subversion 设置了我所有的创意朋友（过去），现在我推荐 Git。即使是那些正在对数百个视频进行视频编辑的人。当他们收到最终付款时，他们可以将项目存档。驱动器空间很便宜，比以往任何时候都便宜，大小在任何现代 VCS 中都不是问题。如果您按小时计费，能够恢复到以前的工作状态或尝试一些东西而不丢失数据并手动管理多个“临时”目录是非常宝贵的。
Version Control Systems are useful for ANYONE that is doing work that they might need an older version of at some later date. That said, I have set up all my creative friends with Subversion (in the past) and now I recommend Git. Even those that are doing Video editing with hundreds of gigs of video. They can archive off the projects when they get final payment. Drive space is CHEAP, cheaper than ever before, size isn't an issue in any modern VCS. Being able to revert back to a previous working state or experiment with something without losing data and manually managing multiple "temp" directories is invaluable if you bill by the hour.
是的，
不用担心大小，如果空间不足，只需购买更大的硬盘即可。
丢失信息的代价将会更高。
除了 VCS（任何都可以，因为您不需要增量存储）之外，还应定期进行备份。
进行签出时，您不应该站在系统的根目录上，而应该站在项目的特定分支上，这样它就不会比该文件夹的任何简单复制操作慢。
Yes
Don't worry about the size, if you run out of space, just buy a larger hard drive.
Losing information will be far costlier.
In addition to a VCS (any will do, as you won't be needing delta storage), do regular backups.
When doing checkout you shouldn't be standing on the root of the system, but rather on a specific branch to your project, that way it won't be slower than any simple copy operation of that folder.
绝对建议对您关心或不能丢失的任何类型的文件使用版本控制。磁盘空间很便宜，正如已经指出的那样，丢失一堆重要文件比多花几块钱买一个新硬盘要糟糕得多。我推荐 Subversion，因为它具有文件锁定功能，这是处理二进制文件和版本控制时的一个重要功能，可以防止丑陋或不可能的合并冲突。
Definitely recommend using Version Control for any type of file you care about, or can't afford to loose. Disk space is cheap, and as has already been pointed out it'd be far worse to loose a bunch of important files than to spend a few extra bucks on a new HDD. I recommend Subversion since it has file locking, an important feature when working with binary files and version control to prevent ugly or impossible merge conflicts.
我相信是这样。特别是如果您希望跟踪一段时间内的更改或需要回滚到以前的版本。如果您担心大小，集中源代码控制可能是一个不错的选择。
I believe so. Especially if you wish to track changes over time or need to rollback to previous versions. Centralized source control may be the way to go if you're worried about the size.