XCode4 GM 生产安全吗？
XCode4 对于生产应用程序安全吗？我想进行更改，但不确定它是否会损坏或导致生产出现问题？
Is XCode4 safe for production apps? I would like to make the change, but not sure if it will break, or cause problems working on production?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我目前正在做一个研究项目，调查 libdispatch.h 与顺序和 posix 线程方法相比的性能，并决定自 XCode 4 的第一个预览版发布以来专门使用 XCode 4，并且可以说 GM 比以前的任何方法都好得多发布。话虽如此，它仍然会莫名其妙地崩溃，通常是在执行简单的 GIT 操作或更改视图时。我只经历过一次碰撞，我觉得这对于通用汽车来说是可以接受的，因为我正在测试一些相当严酷的东西。
XCode 4 GM 覆盖了我的 XCode 3 安装，没有一个预览版做到了这一点，它甚至保留了安装的预览版。这对我来说是一个惊喜，因为我一发布就升级了，他们现在可能会警告你。
尽管他们试图让它变得更简单，但我仍然迷失在用户界面中。祝你好运，找到有关 XCode4 特定功能的帮助，正如预期的那样，关于它的信息还不是很多。在生产环境中，这可能是悲剧性的。
我短暂地玩弄了 InterfaceBuilder，但它真的让我失望，我找不到任何我想要的东西。不过，我使用 IB 的时间不够长，也没有阅读足够多的帮助文档来对其做出判断。
话虽这么说，我仍然在积极使用它并且已经习惯了它。我没有回到 3 的计划，但不建议进行生产飞跃，除非您确实需要新的编译器支持或工具。
I'm currently doing a research project investigating libdispatch.h's performance in comparison to sequential and posix threaded approaches, and decided to exclusively use XCode 4 since their first preview release and can say that the GM is leaps and bounds better than any of the previous releases. That being said, it still crashes unexplainably on me, often when doing simple GIT operations or changing views. I've only had one crash that I felt was okay for a GM, because I was testing something rather harsh.
XCode 4 GM overwrote my XCode 3 installation, none of the previews did this, and it even kept the preview release installed. This was a surprise to me because I upgraded as soon as it released, they may warn you now.
I get lost in the UI still, even though they tried to make it simpler. Good luck finding help on specific features of XCode4 also, there's not a lot of information on it yet, as to be expected. In production environments, this could be tragic.
I briefly toyed with InterfaceBuilder but it really put me off, I couldn't find anything I looked for. I did not use IB long enough or read the help documentation enough to pass judgement on it though.
All that being said, I'm still actively using it and have gotten used to it. I have no plans on going back to 3, but wouldn't recommend making the production leap yet, unless you really need the new compiler support or instruments.
如果您认真对待拥有一个可靠的生产环境，那么您还需要认真对待您的临时环境：您可以在其中模拟（几乎*）完美细节的生产环境。
以与生产环境完全相同的方式（希望是自动化的？）部署到临时环境。然后你可以自己判断它是否会破裂。
中断阶段很便宜，因为在它停止运行时没有人会浪费时间（可能除了其他开发人员）。
中断生产......不是那么便宜，原因相当明显。
If you're serious at all about having a solid production environment, then you need to also be serious about your staging environment: one where you can emulate in (almost*) perfect detail the production environment.
Deploy to staging in the exact same (hopefully automated?) manner as you would to production. Then you can tell for yourself if it will break.
Breaking stage is cheap, because no one is losing time while it's down (except possibly other developers.)
Breaking production ... not so cheap, for rather obvious reasons.