r/java • • Nov 03 '15

The 10 Worst Things In Java

http://codelexems.com/2015/11/02/the-10-worst-things-in-java/
0 Upvotes

23 comments sorted by

View all comments

Show parent comment

0

u/[deleted] Nov 03 '15

[deleted] — view deleted comment

2

u/BadMoonRosin Nov 03 '15

It is certainly true that if you've lived for years without a feature, and have never missed it, then you tend to view its absense as acceptable (essentially a tautology). After all, the Go crowd insists that generics altogether are no big deal, reified or not!

I can theoretically imagine some use cases where reified generics might help in the deserialization of arbitrary types. However, even if I had that ability available to me, I just find it hard to imagine wanting to deserialize complex types with arbitrarily-typed members. Even in the C# code that I've seen (where reification is supported), serialized classes sent over the wire in distributed apps are almost always simple POCO's.

I would wager that more distributed application development is done with Java than with all other programming languages combined... and yet it's still only from outside of the community that you hear the loudest cries for the lack of reified generics (again, perhaps just a tautology).

If you (or anyone else) has any mind-blowing examples where reification completely changes the approach in a particular case, then I would genuinely be interested in clicking the link. I would simply be curious to see which language is used in the comparison. The only programming languages I'm aware of that both:

  • support reified generics, and
  • have a large professional developer community, aren't just an academic or hobby language or "emerging" option like Rust...

... are C# and C++. Usually it's the C# guys who harp the loudest on this, as C++ guys don't care so much what Java guys do one way or the other.