为什么 ruby on Rails 很敏捷？
我总是听说 RoR 有利于敏捷实施。有人可以总结一下这个说法，并用一些例子解释为什么。
PS 我还不能阅读“使用 Rails 进行敏捷 Web 开发”。
I'm always hearing that RoR is good for Agile implementation. Could someone plaese summarize this statement and explain me why with some examples.
P.S I can't read "Agile Web Development with Rails" yet.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在软件工程中，工具从来都不是敏捷的。工具支持敏捷。 Ruby on Rails 是一个可以轻松快速构建基本功能的框架，在大多数人看来，敏捷是一种在不了解系统所需的每个需求的情况下构建系统的方法。
因此，支持开发人员快速启动软件或快速更改功能的工具可以帮助您保持敏捷。因为大多数时候，客户和开发人员对“事物如何工作”的理解是不同的。
协调这些观点是每个项目的成功因素，大多数时候，展示一些有助于达成共识的内容比绘制一些流程图、uml 图表或任何暗示领域知识的内容更好。
另一件事是，如果您可以快速启动一个项目，您可以对优先级的重新排序做出更灵活的反应。
对于挑剔者：敏捷是一个流行词。对于什么是敏捷有很多定义和不同的理解，我对敏捷或开发敏捷的看法可能总是与其他定义不同。
Tools are never agile in the matter of software engineering. Tools support in being agile. Ruby on rails is a framework to rapidly build basic functionalities with ease and Agile in most minds is a way to build your system without having the knowledge of every requirement needed by your system.
So tools which support the developers to rapidly bootstrap a software or change functionalities rapidly help you in being agile. Because most of the times the understanding of "How things work" differs between the customer and the developer perspective.
Aligning those perspectives is a success factor on every project and most of the times it is better to show something for a common understanding than painting some flow charts, uml charts or whatever which imply domain knowledge.
Another thing is if you may bootstrap a project rapidly you may react on reordering of priorities more flexible.
For the nitpickers.: Agile is a buzzword. There are lots of definitions and different understandings whats agile is and it may always be that my view on being agile or developing agile differs from some other definitions.