Groovy / Grails :: Ruby / Rails :: 2011框架状态 [英] Groovy/Grails :: Ruby/Rails :: 2011 State of the framework

问题描述

是的，有几个类似的线程存在，但我们现在在2011年，而且发生了很多变化。

Grails 1.3.6与v1.3相比有了巨大的改进当我最初试图学习框架（并放弃了编译时间缓慢和其他呻吟诱发事件）。

在最新版本上花费了几个月的时间，我留下深刻的印象，protyping应用程序是一个微风（GORM是伟大的！）。在开发模式下，不再需要重新启动，禁止更改域类。 Groovy.lang非常棒（记住，这与我在PHP中的日常工作生活相比）。

现在，另一方面有Ruby / Rails，它我几乎没有经验可以深入了解Ruby文档并探索Active Record（与GORM进行比较）。来自PHP / Jquery的groovy语法是蛋糕，ruby并不是很多，尽管可以访问。

Ruby / Rails非常流行，而Groovy / Grails似乎在挑选

我想听听两个阵营必须说的话（火焰诱导郎战争欢迎）re：两种语言的优缺点/框架现在在2011年。当选择一个框架时，重要的是要知道你正在进入什么，所以拥有它，新手会受益，并且专家可以发泄; - ）

解决方案

Rails和Grails都是当前版本的优秀框架。你真的不能出错。以下是我对它们感兴趣的一些内容：

Rails

• Rails （Ruby）并不像Grails（Groovy）那么好。您将需要更多的马力来运行您的应用程序。对于像EngineYard这样的PaaS选项（未来希望有一个AWS BeanStalk Rails选项），这并没有什么大不了的，但是运行Rails应用程序和Grails应用程序可能只需要一点点（显然JRuby也是一个）。
  
• Rails在目前的NoSQL替代品中略胜一筹，但Grails正在迅速赶上


• Rails有更多的插件，但是这个可能会导致麻烦，如果你使用一些没有维护（其中很多目前还没有使用Rails 3）。


• Rails更成熟，并且具有更多功能这是时间点，因为它已经变长了


• Rails REST支持令人惊叹


• Rails网站比Grails还多很多
>

• Ruby比Groovy更受欢迎 - TIOBE


• 不依赖Oracle，哈！ （Grails显然需要JVM）

Grails

• Grails与JVM的整合优于JRuby


• 虽然Rails 3为其他持久性选项打开了一扇门，但Grails GORM比ActiveRecord（IMHO）更好，但所有书籍，教程等全部使用ActiveRecord


• Grails视图taglibs优于< =％...％>视图


• Grails插件很好记录并明确说明它们是否受SpringSource支持


• SpringSource正在Grails中进行大量投资


• Grails中将有更多的企业作业比Rails在未来，但更多的初创公司使用Rails（你想工作吗？）

我的观点

• 几年前我使用过Rails，现在我正在开发一个Grails项目


• 我喜欢它们都比Django（Python）或Zend Framework（PHP）


• 我计划学习Lift（Sc ala）next

我的建议

• 如果你从未做过Java开发，并且正在为一个中小型网站开发一个项目，请使用Rails


• 如果你在一家使用Java的大公司工作，请尝试投入Grails作为他们应该投资的下一个Java框架给您的管理人员


• 如果您正在研究下一个twitter或foursquare，那么您足够聪明，可以自己回答这个问题！ ：）

Yes, several similar threads exist, but we're now in 2011, and much has changed.

Grails 1.3.6 has improved hugely compared to v1.3 when I initially tried to learn the framework (and gave up to slow compile times and other groan inducing events).

Having spent a couple months with the latest release, I am impressed, protyping an app is an absolute breeze (GORM is great!). In development mode one no longer needs to restart, barring changes to domain classes. Groovy.lang is fantastic (bare in mind, this is compared to my day job life in PHP).

Now, on the flip side there is Ruby/Rails, which I have little experience with beyond perusing Ruby docs and exploring Active Record (to compare to GORM). Coming from PHP/Jquery, groovy syntax is cake, ruby not so much, although accessible.

Ruby/Rails is all the rage, while Groovy/Grails seems to be picking up speed in its own right.

I'd like to hear what both camps have to say (flame inducing lang war welcome) re: pros/cons of both langs/frameworks now in 2011. When choosing a framework it's important to know what you're getting into, so have at it, newbies will benefit, and experts can vent ;--)

解决方案

Rails and Grails are both excellent frameworks with their current releases. You really can't go wrong with either. Here are some things I find interesting about them though:

Rails

• Rails (Ruby) does not scale as well as Grails (Groovy). You will need more horsepower to run your application. This isn't a big deal at all with PaaS options like EngineYard (and hopefully a AWS BeanStalk Rails option in the future), but it might just cost a little more to run a Rails app vs a Grails app (obviously JRuby is also an option to though).
• Rails is slightly better with NoSQL alternatives currently, but Grails is catching up quickly
• Rails has many more plugins, but this can lead to trouble if you use some that aren't maintained (a lot of them don't currently work with Rails 3 yet either).
• Rails is more mature and has more features at this point in time because it's been around longer
• Rails REST support is amazing
• There are many more "big" Rails websites than Grails
• Ruby is much more popular than Groovy - TIOBE
• No dependence on Oracle, ha! (Grails obviously needs the JVM)

Grails

• Grails integrates with the JVM better than JRuby
• Grails GORM is better than ActiveRecord (IMHO), although Rails 3 opened the door a little bit for other persistence options, but all the books, tutorials, etc all use ActiveRecord
• Grails View taglibs are better than <=%...%> in view
• Grails plugins are well documented and clearly state whether they are supported by SpringSource or not
• SpringSource is investing heavily in Grails
• There will be many more corporate jobs for Grails than Rails in the future, but more startups use Rails (where do you want to work?)

My perspective

• I used Rails a couple years ago, I'm working on a Grails project now
• I like them both better than Django (Python) or Zend Framework (PHP)
• I plan to learn Lift (Scala) next

My Recommendation

• If you have never done Java development and are working on a side project for a small to medium website, go with Rails
• If you are working at a big company that uses Java, try pitching Grails to your management as the "next Java framework" they should invest in
• If you are working on "the next twitter or foursquare," well then you are smart enough to answer this question yourself! :)

这篇关于Groovy / Grails :: Ruby / Rails :: 2011框架状态的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！