The Artima Developer Community
Sponsored Link

Java Community News
Peter von der Ahé on the Kitchen Sink Language Project

1 reply on 1 page. Most recent reply: Jan 18, 2007 11:48 AM by Tom Flaherty

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 1 reply on 1 page
Frank Sommers

Posts: 2642
Nickname: fsommers
Registered: Jan, 2002

Peter von der Ahé on the Kitchen Sink Language Project Posted: Jan 11, 2007 1:19 PM
Reply to this message Reply
The Kitchen Sink Language is a new project designed to facilitate experimentation with new language features. In this interview with Artima, Sun compiler lead and Kitchen Sink project owner Peter von der Ahé describes how developers can try out new language features in the context of this project.

Discussions about proposed new Java language features have flared up in recent months on the Web. While some language features, such as closures, have a high chance of being implemented in the next version of the JDK, others are of a more experimental nature. In a recent blog post, James Gosling warns of the dangers of debating the merits of proposed language features without an available implementation of the feature under discussion:

What I don't like is debate divorced from experiment and data. Language arguments can get into all sorts of handwaving without building sample implementations.

Since Sun open-sourced the JDK late last year, implementing new language features has become possible: Anyone can download and modify the Java compiler sources to suite an experimental idea. This week, Peter von der Ahé, Sun's Java compiler lead, created a project, the Kitchen Sink Language, to host just such experimental compiler changes. In an interview with Artima, Ahé described the new project's goals:

It was originally James [Gosling]'s idea, and is something he mentioned a while ago when we started talking about open-sourcing the compiler. He wanted to be able to create a place where you could experiment easily with adding various language features. [That way], we can evaluate those features before we decide to propose them for inclusion in the standard through the JCP. When we decide to do something in the JCP, it's almost a done deal, and is often fully developed. So where is the room to experiment? That's exactly what we can do now that the compiler is open-source. We decided to set up a project so that anyone can join in.

Ahé noted that most submissions to the Kitchen Sink Project will at first be compiler patches already submitted from the community:

Some open-source contributors have already posted [compiler] patches. I'd like to see those incorporated on the Kitchen Sink project. Remi Forax has been writing a few patches, for instance: One is implementing two alternate versions of one language feature where you can leave out the type of a local variable, and the other feature ... is a shorter syntax for accessing properties. He was one of the first people with access to the project's site.

Possible submissions to the project are not limited to the language features currently under discussion. Indeed, Ahé noted that any experimental feature can be submitted:

The idea with Kitchen Sink is that you can add any feature you like, and people can look at it and discuss that based on having tried it out rather than just [talking about] abstract specifications.

We want it to be open for everybody to play around, with the only caveat [being] that people need to sign the Sun Contributor Agreement before they commit anything to this project. There are also some restrictions on the main branch. If you want to commit to the main branch, you have to follow certain rules. If you think that those rules are premature for what you want to try out, we encourage you to create a branch within the Kitchen Sink ... where you can create your own experimental features.

If you want to get your [changes] into the main trunk, then there are some restrictions. One of them is that you can disable the feature, that the feature be controlled by an option, and that it is not enabled by default. There are also a few minor rules about code review and what should be in the comments. Again, that's only for the main trunk.

The benefits of the main trunk is that it's going to be Java, unless you add options to the compiler. And it also will probably be a bit higher quality because of our code review requirement. If you have some crazy idea and, for example, want to replace the entire parser to [parse something] that doesn't even look like Java, that's OK. That would be done in a branch of the project.

What do you think of the Kitchen Sink project's goals?

Tom Flaherty

Posts: 7
Nickname: axiom6
Registered: Dec, 2006

Inspiration Posted: Jan 18, 2007 11:48 AM
Reply to this message Reply
The significant changes proposed for Java focus on the introduction of functional language features beginning with closures.

For inspiration I recommend Scala.

1. Scala is the next phase in the evolution of Java.
2. Scala is the finest example of what can be built on the JVM.
3. Scale make programming fun again.

The name Kitchen Sink Language is priceless.

Flat View: This topic has 1 reply on 1 page
Topic: Yahoo's Tenni Theurer on Client-Side Web Page Caching Previous Topic   Next Topic Topic: What Makes an Ideal IDL?

Sponsored Links


Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use