Everything that's wrong with Java in a single class

Post by patio11 » Fri, Sep 21, 2012, 8:34 AM UTC

taf2 wrote: post #14

bane wrote: post #8

Earlier quoted context omitted.

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.

Either it's the people who write Java, or something intrinsic in the design of the language itself that drives people to write code in this extremely verbose way. I've always leaned towards the latter...

Post by moondowner » Fri, Sep 21, 2012, 9:09 AM UTC

rickmode wrote: post #56

cletus wrote: post #22

I hate this kind of post. It's the tech equivalent of "You're a stupidhead". If you want to criticize Java then at least make some meaningful points. Just off the top of my head: - Java logging is a clusterfuck - Something as simple as wanting symbolic links in a Maven build requires a third party plugin, last updated in 2007 (maven-junction-plugin) that requires something no longer in the central repo; - No lambdas…

The class combines no less than 6 concepts / design patterns: - Abstract - Singleton - Proxy - Factory - Bean - Interceptors It's not just a long name. The class makes sense in the context of this framework. The core problem (as others here point out) is that the Java flavor of OOP makes writing this sort of code idiomatic. On the upside, you feel really smart once you grok all these concepts simultaneously. After a…

Post by DomreiRoam » Fri, Sep 21, 2012, 9:21 AM UTC

rickmode wrote: post #60

cletus wrote: post #36

Earlier quoted context omitted.

Did you read what I said? "vim/emacs are [for Java] no better". This was in part to head off the predictable chimes from some of "all IDEs are stupid, (vim|emacs) is the best thing since sliced bread". My tool of choice for Java is however IntelliJ, which is simply light years ahead of Eclipse (IMHO).

> My tool of choice for Java is however IntelliJ, which is simply light years ahead of Eclipse (IMHO). I agree. Eclipse seems to always become unstable once enough plugins are installed. After a few updates and removals it ends up tipping over regularly. I suspect the underlying OSGi plugin system is a tricky thing to get right. Intellij IDEA seems to "just work". That said, I prefer coding in Clojure with Aquamacs b…

Post by exDM69 » Fri, Sep 21, 2012, 9:33 AM UTC

Post by hythloday » Fri, Sep 21, 2012, 11:27 AM UTC

patio11 wrote: post #111

taf2 wrote: post #14

Earlier quoted context omitted.

Either it's the people who write Java, or something intrinsic in the design of the language itself that drives people to write code in this extremely verbose way. I've always leaned towards the latter...

A bit of column A and a bit of column B. People who write Java are exposed to rampant overuse of design patterns when looking at examples of a) what the community considers Good Java and b) all over their internal projects. This is partially because Java lives, by design, in a Kingdom of Nouns and partially because there's just no good way in the standard language / library / toolchain to do some things without going…

  public class Student implements Comparable {
    @NotNull public List getTests() { ... }
    @NotNull public String getLastName() { ... }
    @Override public int compareTo(Student that) {
      return getLastName().compareTo(that.getLastName());
    }
  }

  List studentsWhoHaveNotTakenAtLeastOneTest() {
    TreeSet studentsMissingAtLeastOneTest = new TreeSet();

    for(Student student : getStudents()) {
      boolean allTestsWereTaken = true;
      for(Test test : student.getTests()) {
        allTestsWereTaken &= test.isTaken();
      }

      if (!allTestsWereTaken) {
        studentsMissingAtLeastOneTest.add(student);
      }
    }

    return new ArrayList(studentsMissingAtLeastOneTest);
  }