Everything that's wrong with Java in a single class
plus.google.com
Everything that's wrong with Java in a single class
1–10 of 159 posts
Re: Everything that's wrong with Java in a single class
#2the source page that the google+ is commenting on was on HN a while back, but didn't get many comments
Re: Everything that's wrong with Java in a single class
#3I'm kind of partial to
com.sun.java.swing.plaf.nimbus.InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneMaximizeButtonWindowNotFocusedState.
A "non-haiku" has been written in its honor:
Re: Everything that's wrong with Java in a single class
#4I'm not sure how one framework developer's naming choice (a framework which by the way, needs to do some pretty meta things in regards to creating factories for other factories, and which is using the term "singleton" to mean something different than usual) is a criticism of an entire language.
You can come up with ugly names for classes in any language.
Re: Everything that's wrong with Java in a single class
#5This is pretty funny, and yes Spring itself is pure insanity, but it's not really fair to equate Java the language with Spring the framework.
Re: Everything that's wrong with Java in a single class
#6I'm not sure how one framework developer's naming choice (a framework which by the way, needs to do some pretty meta things in regards to creating factories for other factories, and which is using the term "singleton" to mean something different than usual) is a criticism of an entire language. You can come up with ugly names for classes in any language.
I think it speaks more to the community than the language (and arguably there is also no such thing as a community).
After years of consulting I can't remember how many times I've walked into an Enterprise Java Shop(TM) to find TemporalSystemLoadOrganizers, IntransitPredeterminedApplicationUtilitySources, MetaphysicalManipulatitiveQuantityDisorderRecognizers only to find out that at the end of the day these abstract-factory-driven-decorated-decoupled-dynamically-injected-frameworks tend to do such obscure/complicated things as "Update a user's first name" or "Show the last item the user has purchased"...
Again, not Java's fault and no question you can write very fast, beautiful and clear code in Java. I'm sure every language has specific warts and most of them probably reside more with the community than the syntax.
Re: Everything that's wrong with Java in a single class
#7Hello and welcome to 2008!
Seriously though, if you are going to rehash this tired schtick then at least make intelligent points about the problems with the language. I have been writing Java for over a decade and I can tell you are a number.
Re: Everything that's wrong with Java in a single class
#8I'm not sure how one framework developer's naming choice (a framework which by the way, needs to do some pretty meta things in regards to creating factories for other factories, and which is using the term "singleton" to mean something different than usual) is a criticism of an entire language. You can come up with ugly names for classes in any language.
I think it speaks more to the community than the language (and arguably there is also no such thing as a community). After years of consulting I can't remember how many times I've walked into an Enterprise Java Shop(TM) to find TemporalSystemLoadOrganizers, IntransitPredeterminedApplicationUtilitySources, MetaphysicalManipulatitiveQuantityDisorderRecognizers only to find out that at the end of the day these abstract-…
Right, it's not the fact that you can name things poorly in any language, it's that non-descriptive, overly verbose word-jumble vomit is built and presented seriously and without irony as common practice.
Re: Everything that's wrong with Java in a single class
#9I'm not sure how one framework developer's naming choice (a framework which by the way, needs to do some pretty meta things in regards to creating factories for other factories, and which is using the term "singleton" to mean something different than usual) is a criticism of an entire language. You can come up with ugly names for classes in any language.
This isn't a verbose naming convention. The name is actually quite succinct in describing what this encompasses.
And that's precisely the issue.
Re: Everything that's wrong with Java in a single class
#10Hello and welcome to 2008! Seriously though, if you are going to rehash this tired schtick then at least make intelligent points about the problems with the language. I have been writing Java for over a decade and I can tell you are a number.
No need to create javadoc, takes people 4 years to read it anyway :D