A good example of bloatware encouraged by a non-expressive language. Instead of adding a language feature that makes constructing any instance easier, in 2013 they're adding support for a builder on a single Calendar class.

    final Calendar calendar =  
       new Calendar.Builder()  
         .set(YEAR, 2013)  
         .set(MONTH, APRIL)  
         .set(DATE, 6)  
         .build(); 

For a similar API in C# you could use named parameters:

   var calendar = new Calendar(year:2013, month:Month.April, date:6);

or just set public properties in an object initializer:

    var calendar = new Calendar { 
      Year = 2013,
      Month = Month.April,
      Date = 6,
    };

Likewise in Dart with named parameters:

   var calendar = new Calendar(year:2013, month:APRIL, date:6);

or using method cascades:

    var calendar = new Calendar()
      ..year = 2013
      ..month = APRIL
      ..date = 6;

For C#, Dart you get this for free when constructing any object. Java requires creating the boilerplate of a builder for every class?? and with all that effort it's still more verbose.

    var calendar = new Calendar()
      ..year = 2013
      ..date = 6;

   Builder.setYear(2012).setDay(60); // February 29

   Builder.setYear(2000).setDay(MONDAY).setWeek(14);
   // Monday of week 14 of week 2000

To be honest, this just seems like bloating the JRE even further with stuff that can be in a library (and is - JODA time?). I can't wait for Java 9 (I think?) that will finally work on modularising the JRE so I don't have to include most of this stuff if not needed...

I was always curious, why they called this class as Calendar. It's actually date/datetime/time.