IronRuby's alive and kicking - and will go 1.0 in July. We look at some resources to get up to speed with IronRuby's status. Also: JRuby 1.3.1 is an important bug fix update for JRuby users, MacRuby continues to improve and MagLev now comes with a native parser.
A DoS vulnerability has been found in all Ruby 1.8.x versions, fixes are now available in 1.8.6-p369 and 1.8.7-p173. Current JRuby versions also seem to be affected.
JRuby 1.3 is now available, bringing performance improvements and compatibility with Google AppEngine. Work on other improvements is continuing and a first version of the ruby2java compiler is now available. Also: InvokeDynamic support is making it's way into the builds for the next Java version.
Aaron Patterson has a solution for native Windows RubyGems that support both Ruby 1.8 and 1.9 at the same time: fat binary gems. Is It JRuby.com tracks JRuby compatibility for popular Gems; and some new RubyGems plugins emerged.
GitHub now offers an installable version of the service for users who want to keep their code inside their network - and it's built on JRuby. TorqueBox is a new solution for running JRuby on Rails on JBoss, complete with integration for job queues and SIP integration Also: EngineYard announced it will start providing JRuby as a hosting option in July.
Dmitry Jemerov is the lead developer of the RubyMine IDE project at JetBrains. RubyMine is the new integrated development environment from JetBrains focusing on helping Ruby and Ruby on Rails developers be more productive and efficient programmers.
JRuby 1.3 will allow to reduce startup times in some situations using Nailgun. Nokogiri, a popular XML library, now runs on the latest JRuby thanks to ruby-ffi. Finally: Ruby 1.9.1-p129 is a new release that fixes a few bugs and security issues.
JRuby 1.3RC1 is now available and includes the changes required for running on Google App Engine. The release also includes a modified version of the timeout functionality. Also: adding Nailgun to the standard JRuby could reduce the impact of Java's slow startup times.
New versions of Ruby 1.8.6 and 1.8.7 are available now. JRuby development moves ahead with experiments with running JRuby on IKVM. Also: MacRuby continues performance work and MagLev now runs RubyGems.
The current Ruby 1.9.1 doesn't have the required features to allow ParseTree's runtime features to work - which means some libraries that depend on those features won't work. Examples are Merb's action arguments or heckle. We take a look at the state of ParseTree - and how ruby_parser is a possible way out.
While JRuby on Rails doesn't have ActiveRecord, DataMapper, an ORM often used with Merb, has gained a new adapter for Google App Engine's DataStore. Also: work on Reggae, automatic tooling for deploying Rack apps on GAE is under way.
SAP, the market share leader in CRM & ERP and second largest business software company is adopting Ruby as part of their SAP NetWeaver and SAP ERP 6.0 solution. ABAP Virtual Machine will be able to run Ruby Code through the Blue Ruby extension. With recent debates on Ruby VMs, we talked with Juergen Schmerder from SAP and Charles Nutter from Sun (JRuby).
With JRuby 1.2 released, the JRuby community is working on new projects such as a new Ruby to bytecode compiler, a standalone JRuby parser and a first release of the bytecode generating DSL Bitescript. Also: JRuby works on Google App Engine's newly announced Java support.
Bruce Eckel’s recent blog post on the legacy left by C++ and Java generated a lot of reaction. While mentioning some design mistakes, he concludes that both languages have had a significant role in programming languages evolution and an important positive legacy. But is it not too early to talk about their legacy?
In this presentation recorded at QCon London 2008, Ola Bini talks about the current status of the JVM regarding languages running on top of it and the need to evolve in order to support dynamic languages.