[prev in list] [next in list] [prev in thread] [next in thread] 

List:       groovy-user
Subject:    Re: [groovy-user] Any reason for why Java (say) 10 could not be like
From:       Robert Fischer <robert.fischer () smokejumperit ! com>
Date:       2009-10-31 17:55:44
Message-ID: 4AEC7A20.30809 () smokejumperit ! com
[Download RAW message or body]

Java will always be statically typed (as noted before), which means there would have to be a 
revolution in type system theory to enable metaClass-style type mangling.

Of course, at the current rate of JVM releases, Java 10 is going to be sometime around 2020 (no, 
really), so who knows what might happen in the next decade.

In the meantime, check out Project Coin: http://wikis.sun.com/display/ProjectCoin/2009ProposalsTOC

~~ Robert Fischer, Smokejumper IT Consulting.
Enfranchised Mind Blog http://EnfranchisedMind.com/blog

Grails Expert Retainer Services
http://smokejumperit.com/grails-retainer/


Moe wrote:
> I am trying to find arguments to why Sun couldn't/wouldn't be able to 
> deliver on functionalities similar to Groovy's in future versions with Java.
> 
> What is the chance of one day Java having all the same functionality and 
> productivity level as Groovy? 
> What are the obstacles?
> What's the time period we are looking at?
> What will that mean for Groovy?
> 
> Is there perhaps a too big difference in philosophy between the two 
> languages that perhaps Java would never be able to deliver on a Groovy 
> language? 
> Is it more likely that Sun might produce an alternative Java language 
> similar to Groovy?
> 
> Any thoughts or information on this?
> 
> Sincerely / Moe
> 
> 

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


[prev in list] [next in list] [prev in thread] [next in thread]