3 ms·
I also don't see that as the primary source of verbosity in Java. In Scala I can do: import com.foo.bar.{Bar => FooBar} But that's mostly just useful for dea
by thescrewdriver 13y ago
I also don't see that as the primary source of verbosity in Java.
In Scala I can do:
import com.foo.bar.{Bar => FooBar}
But that's mostly just useful for dealing with cases where you have to deal with classes with the same name in different packages.
The verbosity in Java comes from a lack of type inference, lack of first-class properties (get/set naming convention doesn't count), and a whole basket of other missing features. Another large contributor to Java verbosity is sadly the the Java culture of over-engineering and resistance to change which has built up over the years (the latter partly in response to the glacial evolution of Java in the last decade).