使用 WAMP、MAMP、XAMPP 等 AMP 软件是个好主意吗？
我知道像WAMP、XAMPP这样的软件可以节省很多困难的配置时间。但是，除此之外，这是一个好主意吗？另一方面，我想坚持传统方法并单独安装每个组件并使用它们。
I know that softwares like WAMP, XAMPP save a lot of difficult configuration time. But, besides this, Is this a good idea? I, on the other would like to stick to traditional method and install each component seperately and use them.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
当然这是个好主意。简单的配置意味着节省时间。节省时间意味着项目可以快速完成。项目的快速完成意味着更多的项目，更多的项目意味着更多的钱。 ：） 哈哈
Of course it's a good idea. Easy configuration means, saved time. Saved time means, projects complete fast. Fast completion of projects means more projects and More projects mean more money. :) lol
这些一体化解决方案专为快速设置和测试而设计。我认为我不会在现场或商业环境中使用它们，因为可扩展性和可靠性成为主要问题。对于开发平台、非常小规模的部署或临时解决方案，它们快速且易于使用。
These all-in-one solutions are designed for quick setup and testing. I don't think I would use them in a live or commercial environment, where the scalability and reliability become a major concern. For a development platform, a very small-scale deployment, or a temporary solution, they are quick and easy to use.
我同意 JYelton 的观点，因为它是为了快速设置，而不是为了现场或商业环境。对于我自己来说，我来自 .NET 商店，并决定兼职开发一个小型个人 PHP 站点，WAMP 方法非常适合让我的服务器快速启动和运行。
它节省了我的时间，让我能够在其他地方进行投资 - 找到适合我的 PHP 工具链，记录服务器与开发环境的差异，记录开发环境设置，以及设置用于在实时服务器上进行测试的暂存子域。
我认为，如果除了智力启蒙之外没有其他原因，那么单独的作品是值得学习的。如果您打算从事 Web 开发工作，那么了解 Web 服务器堆栈的配置是一件非常好的事情；既了解概念堆栈，又了解特定服务器配置的实际配置和实现。
I'd agree with JYelton in that it's meant for quick setup, and isn't meant for live or commercial environments. For myself, coming from a .NET shop, and deciding to work on a small, personal PHP site on the side, a WAMP approach worked quite well for getting my server stack up and running quickly.
It saved me time that I was able to invest elsewhere - finding a PHP toolchain that worked for me, documenting server versus development environment differences, documenting a dev environment setup, and setting up a staging sub-domain for testing on a live server.
I think it's worth learning the individual pieces, if for no other reason than intellectual enlightenment. If you plan on working in web development, understanding the configuration for a web server stack is a very good thing; both understanding the conceptual stack and the actual configuration and implementations of your particular server configuration.