What features would you like to see in Java?

Question

This is a pretty unoriginal question! Where do you stand on the Closures Proposal? What else would you want to see?

For me it has to be a new decimal type which is really a BigDecimal but allows for standard math operations using +, -, x, / etc.

Answer 1

The list of possible items being discussed for Java SE 7 is here:

http://tech.puredanger.com/java7

And predictions for what will actually make it are here:

http://tech.puredanger.com/2008/08/02/java7-prediction-update/

Answer 2

I'd like the switch statement to support Strings, like in C#. Very useful feature in my opinion!

Answer 3

I made a list previously.

I too would like operators for BigDecimals. I'd also like option types (the ability to have the compiler enforce what is allowed to be null and what isn't, eliminating most NPEs).

I'm not convinced on the full closures proposal. The CICE proposal is OK, except for how it overloads the "public" keyword.

Answer 4

A bit more conciseness in the syntax, with a bit of target type inference and (library defined) defaults for very common cases.

For instance:

Map<String,String> map = new java.util.HashMap<String,String>();

should become something like:

Map<String,String> map = new;

Similar for simple anonymous inner classes.

Answer 5

Appart from closures, I'd really like some simple type inference to keep the hassle of using generics down, and language support for composite oriented programming.

Answer 6

Lots for things. I've just got into C# and there are a lot of features I like. The main one being (automatic) properties

Answer 7

Better support for embedding DSL's so that HQL, SQL, XML and other commonly used DSL can be statically verified and compiled.

Answer 8

Reified generics

Answer 9

Nested functions

Example:

public String myFunc(List<Sometihng>list)
{

   boolean myUtilFunc(Something s) =
   {
      return s.toString != ""
   }

   for(Something s : list)
   {
     if(!myUtilFunc(s)
       return  s.toString
   }
   return null
}

Answer 10

I know this is API and not language, but they really need to redesign javax.crypto

Answer 11

As little as possible.

Syntax sugar is very nice, but it also makes the language more complicated for new developers, and makes maintenance more difficult as there are more ways to express the same logic.

I strongly prefer a rich ecosystem of third-party API's (think Apache Commons and the like) and a website like this where you can ask what to use.

Answer 12

I'd really like to have friend classes. This would give a way to cut down greatly on mindless getters and setters, while adhering to SRP and not resulting in package explosion.

Answer 13

const methods

Answer 14

I'd like to see them quit changing the language/APIs for a while and figure out what's needed after the community has had a bit of time to work it out, develop their own things, then standardise.

Answer 15

I would like support of closures (with out an ugly syntax if possible)..

I like what is proposed by Tom, that would be great

Answer 16

Updated or new Swing components.

The results from open-source projects like SwingLabs should be rolled into Java - for example, JXTable, JXLoginPane.

Swing is also missing a lot of modern UI idioms, like an Outlook Bar.

Answer 17

True property support in the language (similar to MyClass.class for class support, but MyClass.myProperty.property type support - as well as automatic handling of property change support).

This is critical for properly implementing binding - the current lack of support is a major problem (it's not just syntactic sugar to get rid of having to type out getters and setters).

Groovy's got this one nailed, and I really hope that Java gets it.

Answer 18

C# style properties.

Answer 19

class import alias - all other languages has got it (event php) and only Java remains without this feature - for big projects its a huge problem. Its quite simple, I don't understand why it was not added in 1.5. It would be really nice to write something like that:

import java.swing.Popup as SwingPopup;
import java.awt.Popup as AWTPopup;

Hope that this will be added some day....

Answer 20

1. Rename java process (every processes that implements by java language will show in processes list are java or javaw), It's hard for specify process.
2. Support Daemon in linux or Windows Service, many times java need to run is backend process.

but I luv it.

Answer 21

A "Money" class, that allows safe monetary calculations, much like one mentioned here.

Answer 22

Java performance is now quite good - honestly at this point I'd even trade 10-15% speed for reduced memory if it were needed. This is a huge hurdle for desktop app adoption (Notes 8 regularly consumes 450MB+ memory with casual usage - 'nuf said). Biggest needs:

user defined value types (like C# struct) - to allow 'inline' class memory usage instead of via reference. Reduces references which are really adding up memory-wise with move to 64-bit.

Stack allocation via escape analysis - to reduce heap usage and GC

MVM - to help pool free heap space among all running programs

Other niceties: unsigned primitives tuples reified generics (should have been done right from the beginning) syntactic sugar to reduce redundant typing (java is very verbose)

Answer 23

I would like the restrictions on calling this and super constructors loosened to allow for the declaration of local variables and the ability to call static methods and methods on objects other than "this".

The current restriction that calls to super or this constructors must be the first statement is often inconvenient and often leads to very torturous code if parameters to the this/super need to be synthesized or manipulated before it can be called.

Answer 24

BGGA closures and reified generics.

Answer 25

Smaller memory footprint.

Answer 26

Mixins, closures and properties.