Re: [jruby-user] JRuby pitch for Java developers?
Paweł Wielgus <[email protected]> Sun, 11 Jan 2015 22:51:54 +0100
| Newsgroups | gmane.comp.lang.jruby.user |
|---|---|
| Message-ID | <CA+hYk8ZVu0tubv6ZGUid64NfuG4KUkXe9hwGdBnAm59u9XuU3A@mail.gmail.com> |
I might not be the best case study but JRuby in my Java applications is used primarly in these situations: 1. Querying application objects in realtime/runtime 2. Creating reports for users in runtime inside application (we have special module for this) 3. Using JRuby scripts for these parts of application that are very likely to change frequently (loading complicated data from xls files on runtime) -- Pozdrawiam, Paweł Wielgus. tel: +48 604 603 546 2015-01-11 22:11 GMT+01:00 Tobias Pfeiffer <[email protected]>: > Hi everyone, > > couple of months back I listened to the Ruby Rogues JRuby episode with > Charlie (http://devchat.tv/ruby-rogues/124-rr-jruby-with-charlie-nutter) > and he said that the "sales pitch" of JRuby to Java developers is very > different than from the one of JRuby for Ruby developers. And ever since > I wondered, what is the pitch for Java developers? > > Java developers here, why do you use JRuby? Which problems does it solve > for you? How can we get more Java people to try out JRuby? > > Thinking of it I can come up with the following points: > > * write code faster/prototyping/quicker changes > * not type annotations everywhere > * easier access to powerful meta programming features > * superb Java integration, e.g. use libraries/other code easily > * integration goes so far that you can package ruby applications as .war > * for a tester: nicer test framework > > That's about what I can think of - and still makes it hard to explain > why people shouldn't just go with languages "born" on the JVM > (Clojure/Groovy/Scala). > > Ideas/Input/Pointers? > > Cheers, > Tobi > > -- > www.pragtob.info > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email