On Wed, Oct 29, 2008 at 11:38 PM, Andrew Lentvorski <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>>
>> On Wed, Oct 29, 2008 at 04:30:06PM -0700, Chuck Esterbrook wrote:
>>>
>>> At the JVM Languages summit, one of the lightning presenters suggested
>>> that we simply stop using Java. Use the JVM. Use Jython, JRuby,
>>> Groovy, etc. But stop using Java which is less productive and produces
>>> more source code for getting the same work done.
>>>
>>> No one objected.
>>
>> I'm not a VM expert but some say the .NET CLR is better for non-Java
>> languages.
>
> The response is mixed.  There was a big conference sponsored by Sun recently
> talking about implementing languages on top of the JVM.  It had some of the
> gurus from Microsoft there, too.

I was at that conference where the functional folks were out in force
including Clojure's author, Rich Hickey. Every other presenter
complained that Java didn't have tail recursion and some people
pointed out that .NET did, perhaps to goad Sun into adding it. Hickey
mentioned that he took some flak for putting Clojure on the JVM given
that it did not have it.

> The CLR gets some things better, but it has its own points of abject pain
> that the JVM manages to dodge, apparently.

Like what?

> It seems like they are about comparable.

As one of the presenters pointed out, as soon as you use a JVM
standard library, you are immediately informed which language you are
supposed to be using:

import java.lang.Object

And it's not uncommon for tools to parse and generate Java source
whereas on .NET these things got abstracted from the get go because MS
was already putting two languages on their VM from the start.

Sun is starting to see the light, but the "one language" mentality
still shows through in various areas.


-Chuck
-- 
http://cobra-language.com/

-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg

Reply via email to