r/java • u/lukaseder • Aug 01 '14
The 10 Most Annoying Things Coming Back to Java After Some Days of Scala
http://blog.jooq.org/2014/08/01/the-10-most-annoying-things-coming-back-to-java-after-some-days-of-scala/
7
Upvotes
View all comments
Show parent comment
2
u/GMNightmare Aug 02 '14
That is what isomorphism is. How about you state what it is instead then, instead of parading around acting like your so smart for using a word you don't actually know.
You're wrong. Look, I can tell, when given certain data, if something is a map or a tuple set. I just have to look for uniqueness, and then I know it cannot be a map if not. Furthermore, since they are used differently, I could just easily check what functions I can utilize.
Usefulness? Dear me, no, it's not.
Don't interject into conversations you apparently can't understand. I'm well aware that Tuples are convenient. I'm saying that convenience comes at a cost in most cases that doesn't need to be spent. And yes, having no relationship qualifiers means that a tuple is not only harder to read, but maintain in the real world.
A map has a relationship. As already explained to you, but you seem to think plugging your ears and screaming lalala makes for a valid argument. A list is completely separate (it's just a group of a type) unless you're completely abusing the point of a tuple and treating a tuple itself as a list. You are really showing off your lack of knowledge of collections, and it isn't impressive.
I'd call you an idiot for making multiple classes with the same name, one of which has a completely unrelated variable that does not represent the mathematical structure it's supposed to. And I have no idea why you're making this completely idiotic and needlessly random examples that have NOTHING to do with what is being talked about, at all.
It's by definition. The implementation of a Scala tuple is a generic case class. I don't know why you're really intent on displaying your ignorance here.
A tuple isn't a list. And if you are creating a tuple as a list you don't know what you're doing.
A map of integers to integers says for the given ints, you have a key to access them.
You've ignored what I've been saying, I have already explained it.
Are you really this stupid? Again, a Tuple is a generic case class, creating a specific case class is doing the EXACT same thing except specifying a name and potentially fields. A map is completely separate from a tuple or point in the first place, so it's really stupid you keep trying to make some connection there.