(Eclipse PDT == Zend Studio 8) 会返回 true 吗？
他们是不是太相似了，又完全不同了？
根据 PHP 风格的比较，即使它们基本相同但不相同，这也会返回 true。 （不是===）
请欣赏任何见解。
免责声明：我确实相信这个问题有一个客观的答案，因为我不是问哪个最好，只是问主要的区别。
Are they too much alike, totally different, neither?
Drawing from PHP-style comparison, this would return true even if they were basically the same but not identical. (Not ===)
Appreciate any insights please.
Disclaimer : I truly believe this question has an objective answer, as I'm not asking which is best, just the main differences.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Studio 构建在 PDT 之上，因此它可以完成 PDT 可以完成的所有操作。碰巧Zend Studio网站有一个它和PDT之间的功能比较，显示Studio 的功能有所不同。
Studio is built on top of PDT, so it can do everything that PDT can do. It happens that the Zend Studio site has a feature comparison between it and PDT, showing where Studio's features are different.
实际上从来没有，因为 Zend 正在推出两种产品，一种是商业产品，一种不是。提供与 PDT 相同的功能将是 ZendStudio 的杀手锏。尽管如此，社区仍可以扩展 PDT 的功能，从而推动 Zend 改进更多 Zend Studio。并且还有改进的空间...
Actually never, as Zend is pushing both products and one is commercial and one not. It will be a killer for ZendStudio to offer the same features as the PDT. Nevertheless PDT can be grown in features by the community, thus pushing Zend to improve more Zend Studio. And there is room for improvement...
我今年年初开始使用 Zend Studio，并且一点也不后悔。 Zend Studio 是专门为处理许多不同的 PHP 特定场景而构建的，具有 Eclipse 的所有功能。我最喜欢的功能是重构代码的能力，使用户能够在整个应用程序中重命名（或移动）变量、类、类方法或函数。 Zend Studio 还具有强大的调试功能，包括代码跟踪、与 Zend Server 的完全集成、隧道、MySQL 透视图、应用内 PHPUnit 代码覆盖率等等。
I started using Zend Studio early this year, and do not regret it one bit. Zend Studio is specifically built for dealing with many different PHP-specific scenarios with all the features of Eclipse. My favorite feature is the ability to refactor code, enabling users to rename (or move) a variable, class, class method, or function across the entire application. Zend Studio also has great debugging capability including code tracing, full integration with Zend Server, tunneling, MySQL perspective, in-app PHPUnit code coverage, and much more.