2 ms·

These things actually exist?!

• userbinator 12y ago
  They do, and I think more unsettling is the fact that they are completely serious about doing these things. The widespread use of IDEs that autocomplete probably leads to a feeling of indifference ("I don't have to type it all anyway.") Also related is the forced convention of requiring one directory nesting level per package name component, resulting in deeply-nested mostly-empty directories that have a tendency to easily exceed filesystem limits. Here's another ridiculous class name found in different project (AspectJ): http://aspectj.sourcearchive.com/documentation/1.6.5plus-pdfsg/HasThisTypePatternTriedToSneakInSomeGenericOrParameterizedTypePatternMatchingStuffAnywhereVisitor_8java-source.html http://aspectj.sourcearchive.com/documentation/1.6.5plus-pdf...
  • tomjen3 12y ago
    Really accurate methods names are a Good Thing, because you are less likely to be surprised at what they do. AbstractProxyFactoryBeanInstanceSingletonCommand is not, because it is too abstract. Typing the name is not so bad though.