I think one of the problems of untyped or weakly-typed languages is that they can be difficult to debug or understand somebody else's code.
I'm a fan of strong typing. I doubt that puts me in the majority here.
Edit: I'm simply stating a personal preference here: I think this will decrease the readability of source code. We don't all have to agree.
Edit: I can see how my original comment was poorly worded. I didn't mean to say, "I think this change will make Java less than a strongly-typed language", I meant to say, "I think this change might make Java read like less than a strongly-typed language".
Usually, I'm not reading a variable's type, unless I'm reading javadocs. Maybe it's that I came to Java from lisp, and tend to prefer inferred type in general, but I find that, at least with the better code that I read, I don't pay much mind to the type declaration. I suppose, if something's written with poor variable naming conventions, it is helpful.
Interestingly, my original background was LISP, too. That's such a different nut, though, that I don't seem to use the same parts of my brain when reading Java code as I did when reading LISP code.
Yes, well-named variables would make my concerns a non-issue. I just don't trust my fellow man much, I guess.
74
u/evil_burrito Mar 09 '16 edited Mar 10 '16
I think one of the problems of untyped or weakly-typed languages is that they can be difficult to debug or understand somebody else's code.
I'm a fan of strong typing. I doubt that puts me in the majority here.
Edit: I'm simply stating a personal preference here: I think this will decrease the readability of source code. We don't all have to agree.
Edit: I can see how my original comment was poorly worded. I didn't mean to say, "I think this change will make Java less than a strongly-typed language", I meant to say, "I think this change might make Java read like less than a strongly-typed language".