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.
[ Parent
| on HN ]
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.
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.