News for hackers. Stuff that matters.
Re:Why Java? Tales from a Python Convert by dragonwriter on Tuesday December 08, 2015 @07:33PM (#10700972)
Java provides less of the benefits of static typing than many other statically-typed languages (even than others available on the JVM), at a much higher cost in required ritual invocations made to the type system.

Yes, there is a value in static typing, but that value is minimized when you have a type system that isn't particularly expressive and/or have to make add a lot of redundant code to satisfy a comparatively unsophisticated type checker.

Java may have gotten slightly better since its poor performance in cost:benefit terms when it came to static typing helped launch the surge in popularity of dynamic languages, but its still not a great poster child for the benefits of static typing.

Re:Why Java? Tales from a Python Convert by dozzie on Wednesday December 09, 2015 @06:27AM (#10703070)
> Java provides less of the benefits of static typing than many other statically-typed languages

Don't let Java's type declarations fool you into thinking that Java is statically typed. It's still dynamic typing, with merely some kind of type hints slapped on top to be checked at compile time.

Re:Why Java? Tales from a Python Convert by codingbinary on Tuesday December 08, 2015 @10:49PM (#10701788)
And don't forget Java's type erasure. Still wondering how they could actually call that a FEATURE.
Re:Why Java? Tales from a Python Convert by potatosareok2 on Wednesday December 09, 2015 @12:34AM (#10702096)
Was erasure necessary to maintain backwards compatibility?

Also what are you doing that you need type information at runtime?

Re:Why Java? Tales from a Python Convert by codingbinary on Wednesday December 09, 2015 @05:16PM (#10707170)
Type Erasure is the reason you can't use builtin types as generic arguments. And in a lot of cases it forces you to cast.

And as type erasure happens very, very early in the compilation process, you lose a lot of static type information the compiler could act on or give you warnings.

Re:Why Java? Tales from a Python Convert by dmm on Wednesday December 09, 2015 @06:53AM (#10703125)
No it wasn't necessary to maintain backwards compatibility. Type erasure was implemented to allow libraries to upgrade to generics without breaking compatibility with existing applications.
Re:Why Java? Tales from a Python Convert by wtetzner on Wednesday December 09, 2015 @11:14AM (#10704504)
How is that not backwards compatibility?
Re:Why Java? Tales from a Python Convert by codingbinary on Wednesday December 09, 2015 @05:16PM (#10707172)
The one is on a language level, the other on an application/framework level.