Tom Enebo explains reasons for choosing JRuby: Hotspot optimizations, JVM Garbage Collectors, tools like profilers. Also: how JRuby helps to write cleaner, more expressive code with Java libraries.
Thomas Enebo has been a practitioner of Java for over a decade and he is the co-lead of the JRuby project. Thomas has also been happily using Ruby since 2001. In addition to working on JRuby, Tom is interested in improving the state of alternative languages on the Java Virtual Machine. Tom is employed working on JRuby full time at Engine Yard.
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
Java in the Ruby? I shudder
If you Java-ified Ruby, we will have more developer-tools and more e.g ant, maven, other many just for 'making'.
And fewer and fewer apps/
How many Java forums to challenge PhpBB, Moodle etc? Wikis?
Re: Java in the Ruby? I shudder
can you tell me the url of the article?thanks in advance
Re: Java in the Ruby? I shudder
I read that article about 3 years ago, and right now I cannot find it on Google.
I want to apologize if I've sounded like a troll here.
(1) I have nothing against the author/Enebo or the project.
(2) I am not even against JRuby. I am even agitating the use of JRuby in my local Ruby user Groups. I am all for calling Java/C++/Lisp from Ruby.
What I can't stand is what I would call Java-ism. esp. DOWN WITH THE SUN!
(1) When Bruce Tate talked about bloat in his "Faster, Lighter, Better Java," I don't agree.
(2) When DHH and team separated out a lot of stuff from Rails core, I don't agree.
I like bloat. We need bloat. e.g. Why don't DHH team take out ActionMailer from core? Go ahead email is not core to MVC, right?
Every popular/useful language/framework grows. We welcome it. But how it grows can often rub us the wrong way. eg. Java Swing, JMX API, EJB, JDO, so many API's made in SUN! May SUN rest in Peace!
Suppose, if I design Rails 34.56, I would like it to include modules for
(1) rendering views in iPhone platform
(2) rendering views in Symbian platform
(3) rendering views in Android platform
(4) rendering views in some other unknown mobile platform
(56) integrating with popular CMS like Plone, Zope, Joomla etc
(78) Calling Erlang
(79) calling Thrift
What is wrong with that?
We are not mono-cell amoebas. How did we grow our eyes, ears, legs, limbs?
The more complex, the better! The more bloat, the higher up in the food chain!
Go argue with Evolution, with Biology.
But, Evolution didn't work like SUN architects. When you get your left toe hurt, you suddenly don't get a headache or an eye blur or a stomach ache. What I am talking here is MODULARITY from the user's perspective. IS THAT TOO deep to understand for SUN/Java API designers?
SUN is declining, or we may have to learn EJB 12.56 etc. How many Java API's have gone down the drain?
Joel Spoloky says we programmers don't read, not even our own industry's history.
No time for Biology and Evolution?
Fine, please read Robert Glass, at least.
IF I SOUND arrogant/angry, please bear with me. I AM JUST TYPING IN A rush.
I love you all ;-)