From: Patrick Chanezon <chanezon@...>
Date: 2006-03-16T02:21:57+09:00
Subject: Re: Ruby for Java Folks?

------=_Part_2250_32628358.1142443300876
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

One topic that I haven't seen covered anywhere and would find useful is a
mapping between java and ruby libraries, organised by application domain,
and their differences in functional coverage: java is more than a language,
it's a platform and people spend more time learning libraries than the core
language.
One common question for a java developer starting ruby is: in java I would
use this lib to perform that task, what should I use in ruby?
I guess we should have a wiki page with that.

For example
domain: http
jakarta http-utils -> http-access2, open-uri

P@

On 3/15/06, Eric Schwartz <emschwar@fc.hp.com> wrote:
>
> I've agreed to give a brief talk on Ruby for the Pikes Peak Java
> Developers Group.  I've done stuff like this before at work, but that
> was for a crowd coming from a background of shell scripting and Perl.
> I'm not much of a Java guy myself, but I know there's a lot of overlap
> between the Java and Ruby communities.  I can easily spend 45+ minutes
> on Ruby no matter what, but if any of you have any suggestions on what
> an audience of Java programmers would be interested in, I'd welcome
> suggestions.
>
> Here's some topics I plan to cover:
>
> * Everything's a class.
> * Interpreted vs. compiled, and how that affects
>   both language design and performance.
> * Static vs. dynamic typing, leading into
> * Duck typing.
> * Modifying library classes.
> * Modifying individual objects-- emphasis on
>   using this for testing frameworks.
> * Briefly cover Test::Unit and maybe JRuby.
>
> This is all subject to modification.  I may bring Test::Unit in
> earlier, when I tart talking about duck typing.  I don't, I think,
> want to get into too much comparison between the two languages-- these
> are very knowledgable Java people, much more so than I am.  My best
> approach, I think, is simply to present Ruby to them as a fun
> language, perhaps for prototyping Java solutions, ideally as an end in
> itself.
>
> Any ideas on what else I should cover, or if I should de-emphasize
> some of what I listed above would be welcome.
>
> -=3DEric
>
>


--
Patrick Chanezon, AdWords API evangelist
http://blog.chanezon.com/
http://www.google.com/apis/adwords/

------=_Part_2250_32628358.1142443300876--