Grails vs Roo - 为什么SpringSource推出两种非常相似的技术？ [英] Grails vs Roo - why SpringSource is pushing two very similar technologies?
问题描述
任何人都知道这些技术是如何相互关联的，他们会被合并，还是其中一个会被抛弃？另外，Grails和Roo之间有什么重要的技术差异吗？
SpringSource 的目标是让人们尽可能快速和轻松地构建，运行和管理基于Spring的解决方案。我们有 Grails 和 Spring Roo 是因为我们非常关心开发人员的工作效率，毫无疑问，这两种工具都能够极大地提升团队在Spring之上的实力。
<我们有两种技术，因为Roo和Grails在哲学层面和实现层面有很大不同（正如其他回复中已经提到的那样）。每种技术都以我们如何使用这种语言和操作模式组合，使价值主张令人难以置信的好为理念，接近其主要语言（Java或Groovy）和运营模式（开发时间或运行时间）。因此，您将看到每种技术都采用了不同的风格，以最大化该组合（Roo的Java +开发时间或Grail的Groovy +运行时）以及相应的优势。
这些差异实际上是非常积极的，因为它们意味着Spring社区可以选择他们喜欢的生产力解决方案的风格。围绕语言选择和运行时/开发时间操作的这些初步差异立即显现出来，但Grails或Roo的选择还扩展到更加微妙的考虑因素，例如所使用的默认技术，用户交互模型，IDE支持，依赖关系，标准，路线图，扩展等。几乎所有这些差异都是追求针对特定语言风格的最佳解决方案的自然结果。
我们最好的建议是考虑两种解决方案。每个人都有他们的甜蜜点，但两者之间存在差异，这会使您的整体体验在某种情况下通过一种技术或另一种技术得到改善。两份参考指南详细介绍了各自的优势 > 每个解决方案。当然，请记住，尝试两种方法的时间投资是最小的。在10分钟内，您可以在Roo或Grails中构建项目，因此请尝试一下，看看您对于您具体的背景和项目需求是否更自然。
SpringSource (now VMWare) has two very similar technologies: Grails and Spring Roo. I have been using Grails, but I see that SpringSource is actively working on something that is a competitor for that technology and that makes me worried about the future of Grails.
Does anyone know how these technologies relate, are they going to be merged, or one of them will be abandoned?
Besides, are there any important technical differences betweent Grails and Roo?
SpringSource's goal is to make it as fast and easy as possible for people to build, run and manage Spring-based solutions. We have both Grails and Spring Roo because we deeply care about developer productivity and unquestionably both of these tools deliver a serious boost to what teams can achieve on top of Spring.
We have both technologies because Roo and Grails are very different at philosophical and implementation levels (as already noted in the other replies). Each technology approaches its primary language (Java or Groovy) and operating model (dev-time or runtime) with the philosophy of "how do we make the value proposition unbelievably good using this language and operating model combination?". As such you'll see each technology adopting a different style that maximises that combination (Roo's Java+Dev-time or Grail's Groovy+Runtime) and the commensurate benefits.
These differences are actually very positive, because they mean the Spring community can chose which "flavour" of productivity solution they prefer. While these initial differences around language choice and runtime/dev-time operation are immediately apparent, the choice of Grails or Roo also extends to more subtle considerations such as the default technologies used, user interaction model, IDE support, dependencies, standards, roadmap, extensions etc. Nearly all of these differences are a natural consequence of pursuing a best-of-breed solution for a particular language style.
Our best advice is to consider both solutions. Each have their sweet spots, but there are differences between the two which will make your overall experience better with one technology or the other in a given context. Both reference guides detail the respective benefits of each solution. Of course, remember the time investment is minimal in trying both out. In 10 minutes you can build a project in Roo or Grails, so give them a try and see what feels more natural for you given your specific background and project needs.
这篇关于Grails vs Roo - 为什么SpringSource推出两种非常相似的技术？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
