From: Robert Dober <robert.dober@...>
Date: 2010-05-01T17:31:26+09:00
Subject: Re: Inverse of stream parser

On Sat, May 1, 2010 at 9:52 AM, Florian Gilcher <flo@andersground.net> wrote:
>
> On May 1, 2010, at 2:17 AM, Robert Dober wrote:
>
>> On Sat, May 1, 2010 at 12:04 AM, Tony Arcieri <tony.arcieri@medioh.com> wrote:
>>> On Fri, Apr 30, 2010 at 2:32 PM, Brian Candler <b.candler@pobox.com> wrote:
>>>
>>>>> Would you care to use JRuby?
>>>>
>>>> I don't mind which stream parser, but Java is out :-)
>>>>
>>>
>>> Why?
>> And to add insult to injury, by interfacing J*** ;) with JRuby you do
>> not even see Java, you see a Ruby API.
>> ( Just wanted to be clear about this )
>
> Just to be clear, too: By interfacing Java with JRuby, you get a Ruby API that feels like its written by a Java consultant struggling on his first steps to learn Ruby.
>
> While I am impressed how well the integration of JRuby into Java works, Java libraries without a handwritten layer above them still feel very alien. So, you do see Java - a lot, actually.
agreed, I was putting my bold statement to test, when calling into
Java you need to honor the java type checks and there are no block
parameters.
Thus there remains lots of work to be done to adapt a given API to be
"rubyish" my bad.
R.

-- 
The best way to predict the future is to invent it.
-- Alan Kay