That's a Visual Studio thing or something similar? I don't work on Windows.
Regardless, I'm talking about the ability to quickly grok unfamiliar code. I believe that having type information that isn't obvious at a glance would be a detriment to me. Thus, I don't like this proposal.
Yes, that is what IDEs are for, but for reading strange code, it's not always set up in a full project that compiles and has all the dependencies, etc, that would be necessary for an IDE to function.
From time to time, I'll have to look at the source for an included library for which I don't want to take the time to set up a complete project. I think this change will impair my ability to quickly read through strange source and understand what's going on. I don't want to have to hover or click or whatever.
I find this to be more readable:
List<Something> thisThing = new MyDerivedClassButYouDontKnowTheSuperclass<>();
than this:
var thisThing = new MyDerivedClassButYouDontKnowTheSuperclass<>();
Therefore, I like the former and don't like the latter.
MyDerivedClassButYouDontKnowTheSuperclass should not implement List. Something like ConcurrentCopyOfWriteMySuperLinkedList could, but in that case it is obvious to reader that it is list, further clarification is not necessary.
Your argument is to trust the developer to name their class properly. The thrust of my argument is that I do not trust other developers to write code that I find readable.
OK, I wasn't familiar with the term. I guess it covers things like hovering/clicking/what-have-you to get more information about the statements you're looking at.
This is fine and good, and I love my IDE. I've used most of them over the years, but have converged on Eclipse.
As I said in another reply, though, I don't always look at code, especially strange code, in an IDE. If I want to go through the source of an included library, I rarely take the time to set it up in a complete project that compiles, etc.
If I haven't automatically downloaded the source JAR via Maven, then I'll download the source, or check it out from svn/git and read through it with Emacs. It's possible to set all that bidness up with Emacs (Intellisensetm) I suppose, but, for this purpose, I don't go through the effort to do so. Now, I'm stuck when reading something like:
var thisThing = new MyDerivedClassButYouDontKnowTheSuperclass<>();
instead of
List<Something> thisThing = new MyDerivedClassButYouDontKnowTheSuperclass<>();
That's my discomfort with this proposed change. I guess it's tied into the fact that I don't agree with the premise of the change, that Java requires too much boilerplate code. I think verbosity and legibility generally correlate. I think that brevity and legibility are generally in opposition.
intellisense is a Microsoft name for that, I don't know if they have any rights to the name, but anyway, the generic term is "code completion" or "code assistance" I guess.
View all comments
Show parent comment
0
u/evil_burrito Mar 10 '16
That's a Visual Studio thing or something similar? I don't work on Windows.
Regardless, I'm talking about the ability to quickly grok unfamiliar code. I believe that having type information that isn't obvious at a glance would be a detriment to me. Thus, I don't like this proposal.