4 ms·
> Nothing! The problems occur when people think that it's not. I don't really understand what you are trying to get at. Is it wrong or it isn't? The hipster
by ww520 14y ago
> Nothing! The problems occur when people think that it's not.
I don't really understand what you are trying to get at. Is it wrong or it isn't?
The hipster comment is spotted on. This post is evident of that attitude. The OP has to dig up an internal class whose name is probably generated to bash Java. And your original comment basically went further and claimed this long class name is the evident of what is so wrong with Java in general.
If there's no pressing pressure to refactor, then it has work well for its purpose. You want to limit class name to 8 characters to force programmers to pick shorter name? It's an internal class, for god sake. What's the impact on 99.99% of the programmer out there?
Development is a process of compromise and trade-off. Developers don't have infinite time and infinite budget to code. They have to pick their battle and do the more important things.
- javajosh 14y ago1. Java programmers usually don't think of Java as imperative. This leads to problems. 2. The phrase you're looking for is "spot on". 3. Generated code is a code smell. Again, you see a confusion between static and dynamic behavior.
- ww520 14y ago1. You seem to know what most Java programmers think. What do Java programmers think of Java as if not imperative? And what is the thing that they assume Java to be leads to problems? Again what specific problem is the long class name causing? 2. Thank you for correcting my grammar. BTW the period goes inside the quotation marks as in "spot on." 3. While not often used, generated source code are useful as design calls for it. Not everything revolves around static and dynamic.
- ygra 14y ago2. Both styles are valid and used (just be consistent about it in a single body of text). Arguably the period after the quotation marks more closely matches the actual sentence structure.