Cool Code
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
News
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Presentation: Evolving the Java Language
Posted by Dave West on Apr 24, 2009
Neal Gafter on Evolving the Java Language
Neal starts off by reframing his presentation; from the original question, "what is it like to evolve a mature language?" to, "what is it like to evolve a widely deployed language?" The latter question exposes the real issues involved, which include:
- Behavioral compatibility with existing APIs;
- Choosing appropriate design principles that, in turn, influence the choice of new features;
- Examination of the best ways to modify, extend, or add features; and,
- Keep in mind additional long term goals so that immediate improvements do not heedlessly impair the possibility of reaching those goals.
The two categories of immediate short term design goals discussed by Gafter include: Regularize the existing Language and increase modularity. In the first category, issues like fixing type inference, limited operator overriding, and improved catch clauses were noted. Details and examples of these are presented and discussed. The presentation concludes with a discussion of specific long term goals for future extensions and improvements for Java.
View Neal Gafter on Evolving the Java Language for details.
RelatedVendorContent
18 agile and lean practices for effective software development governance
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Bottom line
by
Dan Tines
Posted
Re: Bottom line
by
Leonardo Vargas
Posted
Re: Bottom line
by
Christian Gravata
Posted
Re: Bottom line
by
Dan Tines
Posted
Outdated Bio
by
Oli c
Posted
ok...
by
Ivan Lazarte
Posted
Stale content
by
Neil Bartlett
Posted
Not very informative
by
Christopher Churchill
Posted
-
This was obviously made before the Oracle takeover.
The best thing for "Java" would be to port C# to the JVM. -
C# for Java already exists. For more information see dev.mainsoft.com/Default.aspx?tabid=177
-
Doesn't Neal Gafter work for Microsoft now?
-
C# == Java port to the MS JVM (CLR)
-
so why is type inference (the hashmap => map assignment) a potential feature, but the put/get example not.
generics still seem arbitrary to me - a system that meets someones stringent criteria, but not the majorities expectation. -
This video was recorded in March 2008. Given how quickly things change, it would be nice to see some fresh content.
"Info: Tracking change and innovation in the enterprise software development community"... one year after it happens. -
No, C# evolved. Java didn't
-
Neal gafter sucks. Josh bloch does a far better job at these kind of improvements to the JDK platform. Dunno what he is upto.
8 comments
Watch Thread Reply