[转] JRuby 1.0.0RC3 Released!

转自: http://docs.codehaus.org/display/JRUBY/2007/06/02/JRuby+1.0.0RC3+Released%21

The JRuby community is pleased to announce the release of JRuby 1.0.0RC3.

Homepage: http://www.jruby.org/
Download: http://dist.codehaus.org/jruby/

This will likely be our final release candidate before our 1.0 release. People are
encouraged to try out this release to help us find any remaining showstopper issues. We
have spent a lot of time over the last month squashing compatibility bugs and we have
confidence that applications 'will just work' (tm)*. Please try your applications and
libraries against JRuby and give us feedback.

In the last month we have had a record number of people come in and provide a patch or
report a bug. Interest in JRuby has exploded since JavaOne and RailsConf, and many
development groups are now testing and deploying JRuby and JRuby on Rails apps in
production. This has really helped accelerate our progress and JRuby is looking much
better because of it. A few honorable mentions go out to: Koichiro Ohba, Daniel Berger,
David Montag, Dr Nic Williams, and Jon Tirsen.

We also want to thank all the people who hang out on IRC, triage/report/patch issues, and
communicate on our mailing lists. Their interest has really helped shape JRuby into a
better implementation.

As we approach our 1.0 release, we encourage Ruby (and JRuby) community members to
contribute to a few projects key to the success of alternative implementations:

- The RubySpec Wiki (www.headius.com/rubyspec) has slowly been growing into a free,
community-driven specification of Ruby. Many people have contributed articles, and several
of those directly aided JRuby development. The more people contribute to the wiki--in any
way--the more it will begin to form a complete specification for Ruby the language and
Ruby the platform. Have you written RubySpec today?

- Both the Rubinius and JRuby projects have been building out their testing suites, to the
point that JRuby now runs more regression/compatibility tests than any other Ruby
implementation and Rubinius has the largest collection of RSpec specifications for Ruby.
We two projects have been coordinating and cooperating on these testing/spec suites, but
they need your help! Check out the JRuby or Rubinius source code and dig into the tests...
you'll be helping both projects and the community at large. For more test suites, check
out the RubyTests project on RubyForge, where it is hoped that all test suites will
eventually reside, and the ruby_test project under the Shards project on RubyForge.

JRuby's tests are at http://svn.codehaus.org/jruby/trunk/jruby in the test dir.
Rubinius's specs are at http://code.fallingsnow.net/svn/rubinius/trunk in the spec dir.
RubyTests is at http://rubyforge.org/projects/rubytests
RubySpec is at http://www.headius.com/rubyspec

* - The trademark is a joke

期待ing

目前在做的几个事情，都和Rails相关
1、在熟悉Rails，权衡再三，放弃PHP、放弃Python/Django、放弃ASP.NET,选择Rails, 用作网站搭建
2、比较了Struts2.0, JBoss Seam, 以及传统的SSH组合，最后考虑使用Seam,基于EJB3这样一个轻量级的框架，开发业务系统(貌似不相关，但因为之前考虑过用Rails做业务系统)
3、现在我们又有了JRuby, 将来无论是做网站还是做业务系统；一方面可以将Java引用到Ruby中（似乎看到了可以在Ruby/Rails中使用JFreeChart了），另一方面，可以直接把Java中MVC这个front-end这块用JRuby替换了。

“考虑过Rails做业务系统”

后来基于什么原因给放弃了？现在也在考虑全面转入Rails做开发的评估，很想受教一下。

不知道大家有没有听说过Grails(Groovy on Rails)，效率要比RoR好很多，不妨考虑一下

1. 第三方可用资源现在还不丰富，流行的基于Rails的开源项目也不多。简单打一个比方，要使用Rails来做一个统计图，我们知道在Java中有一个已经发展多年的JFreeChart库。Rails将来肯定也会有，现在即便是有，也难堪大用。

2. 对新生事物的不信任感，虽然Rails在开发效率上大幅提高，比方说以前Java 200个人月能做的事情，Rails只需要40个人月；但这个人月计算，不是说40个人做5个月，变成了40个人做1个月，也许仍然需要5个月，只是人数从从40个人变成了8个人。而且做业务系统，稳定可靠是要追逐的价值。
Java语言本身比较“傻”，但借助良好的开发辅助工具和现有丰富的第三方资源库，照样能有比较好的开发效率。

3. 然后在说说JRuby，一方面解决了现有Rails现有资源相对匮乏的问题，另一方面传统的Java web-MVC是在是越来越不合现在程序开发越来越挑剔的口味，JRuby可以在Web app 中的front-end这块找到自己的定位（其它方面也似乎大有可为）。做程序也一样，避重就轻，趋利避害，什么好用就用什么。JRuby提供了额外的选择。

除了“效率”之外，好像还有很多重要的东西，Grails现在人力资源似乎很有限，到目前为止，GORM还有很多重要的功能没有实现，离实用化还有一段距离呢，慢慢磨吧。

http://www.infoq.com/cn/news/2007/05/fiveruns-manage-suite

真是令人印象深刻，待以时日，基于Rails构建的企业业务系统，将大流行。如果编程不是为了吃饭，我也要用Rails做更加多的事情。

1.0正式版已经发布了！