Synonyms for jruby or Related words with jruby

jython              clojure              ironpython              haxe              ironruby              applescript              cpython              visualage              cakephp              symfony              powerbuilder              beanshell              wxwidgets              autoit              javafx              dotnet              ocaml              angularjs              codeigniter              bioruby              coffeescript              xunit              microedition              msbuild              openjdk              snobol              netbeans              livescript              glibc              gnustep              xcode              turbogears              aspectj              laravel              rexx              grails              kixtart              winrt              mingw              npapi              fltk              rubygems              jquery              vaadin              systemd              clang              powershell              msvc              webdna              libxml             



Examples of "jruby"
JRuby has supported compatibility with Ruby MRI versions 1.6 through 1.9.3. JRuby 1.0 supported Ruby 1.8.6, with JRuby 1.4.0 updating that compatibility to Ruby 1.8.7. JRuby 1.6.0 added simultaneous support for Ruby 1.9.2, with JRuby 1.7.0 making Ruby 1.9.3 the default execution mode (Ruby 1.8.7 compatibility is available via a command-line flag). JRuby 9.0.0.0 added support for Ruby 2.2.
In July 2009, the JRuby developers left Sun to continue JRuby development at Engine Yard. In May 2012, Nutter and Enebo left Engine Yard to work on JRuby at Red Hat.
JRuby packages are available for most platforms; Fedora 9 was among the first to include it as a standard package at JRuby 1.1.1.
Since early 2006, the current JRuby core team has endeavored to move JRuby beyond being a simple C port, to support better performance and to aid eventual compilation to Java bytecode. To support this end, the team set an ambitious goal: to be able to run Ruby on Rails unmodified using JRuby. In the process of achieving this goal, the JRuby test suite expanded to such extent that the team gained confidence in the "correctness" of JRuby. As a result, toward the end of 2006 and in the beginning of 2007, they began to commit much more complicated redesigns and refactorings of JRuby's core subsystems.
JRuby is similar to the standard Ruby interpreter except written in Java. JRuby features some of the same concepts, including object-oriented programming, and dynamic-typing as Ruby. The key difference is that JRuby is tightly integrated with Java, and can be called directly from Java programs. Java has significant footing in the development of web applications.
In July 2009, the core JRuby developers at Sun Microsystems, Charles Oliver Nutter, Thomas Enebo and Nick Sieger, joined Engine Yard to continue JRuby development. In May 2012, Nutter and Enebo left Engine Yard to work on JRuby at Red Hat.
JRuby 1.1 added Just-in-time compilation and Ahead-of-time compilation modes to JRuby and was already faster in most cases than the then-current Ruby 1.8.7 reference implementation.
JRuby can just as easily be called from Java, using either the JSR 223 Scripting for Java 6 or the Apache Bean Scripting framework. More information on this is available in the JRuby Wiki article.
Project Kenai was built using JRuby, Glassfish V2, and MySQL databases.
Geocoder has been fully tested with Ruby 1.8.7, 1.9.2, and JRuby 1.5.3.
JRuby has been able to run the Ruby on Rails web framework since version 0.9 (May 2006), with the ability to execute RubyGems and WEBrick. Since the hiring of the two lead developers by Sun, Rails compatibility and speed have improved greatly. JRuby version 1.0 successfully passed nearly all of Rails's own test cases. Since then, developers have begun to use JRuby for Rails applications in production environments.
JRuby, but Java coding can also be used to call DataMelt numerical and graphical libraries.
While the deal was still pending regulatory approval, the JRuby team collectively resigned from Sun and moved to Engine Yard.
JRuby's lead developers are Charles Oliver Nutter and Thomas Enebo, with many current and past contributors including Ola Bini and Nick Sieger. In September 2006, Sun Microsystems hired Enebo and Nutter to work on JRuby full-time. In June 2007, ThoughtWorks hired Ola Bini to work on Ruby and JRuby.
, there are a number of alternative implementations of Ruby, including [[JRuby]], [[Rubinius]], [[MagLev (software)|MagLev]], [[IronRuby]], [[MacRuby]] (and its iOS counterpart, [[RubyMotion]]), [[mruby]], [[HotRuby]], [[Topaz (Ruby implementation)|Topaz]] and [[Opal (Ruby implementation)|Opal]]. Each takes a different approach, with IronRuby, JRuby, MacRuby and Rubinius providing [[just-in-time compilation]] and MacRuby and mruby also providing [[ahead-of-time compilation]].
Ruby on Rails 3.0 has been designed to work with Ruby 1.8.7, Ruby 1.9.2, and JRuby 1.5.2+; earlier versions are not supported.
The Netbeans Ruby Pack, available in NetBeans 6, allows IDE development with Ruby and JRuby, as well as Ruby on Rails for the two implementations of Ruby.
JRubyArt (formerly named "ruby-processing") is a wrapper for Processing in the Ruby (language), that runs on the Java platform using JRuby.
In a real Mongrel web server application tested in 2007, JRuby performance is better than Ruby MRI 1.8, after the Java Virtual Machine had been instantiated.
In a 2007 benchmark of Ruby implementations, JRuby was faster than Ruby MRI 1.8 in some tests, but YARV outperformed both of them.