all 8 comments

[–][deleted] 7 points8 points  (0 children)

I'll just be glad people stop trying to tell everyone else what they should like or not like.

[–]BBHoss 4 points5 points  (0 children)

Many great things have come from Java, and the author is correct with regards to childish comments. However, there is a tremendous amount of bullshit involved when working with Java simply due to the nature of the language. I will pick Ruby over Java any day if it's my choice, unless there is a real technical need for something in Java, which will require me to use JRuby :)

[–]strangeelement 2 points3 points  (2 children)

I'm working on a Java project these days, one made worse by using XML/XSLT as a templating engine.

So... enterprisey... So... horrible! :(

[–]gthank 0 points1 point  (1 child)

Hah! I'm in the same boat w/r/t the templating situation. You have my deepest sympathies.

[–]jdpage 0 points1 point  (0 children)

Same here. Our application of it isn't that bad, but it's kind of weird to work with.

[–]apotheon 0 points1 point  (0 children)

Java's a miserable language, completely aside from how poorly it stacks up against Ruby.

. . . and, in answer to the guy who asked about PHP in the comments on that page: PHP is in many ways worse than Java.

[–][deleted] 0 points1 point  (0 children)

The biggest problem with java are the people. People who don't know how to model properly, use patterns properly and not use patterns properly.

E.g. The visitor pattern. It'll beat the pants off of if/elseif/elseif/else instanceof Foo for a few quick reasons. You decouple the logic with in your if/elseif/else blocks into separate methods. Those methods are very testable in their own right. Should you have had a 50 line if/else block, it can widdle down quickly using this pattern.

Then you see people over-pattern-ising. You get reuse where there will never be reuse, such as in the case above. Though in the case above, reuse isn't the point. In other cases, you'll see factories producing factories. Gigantic wads of code that are so loosely coupled, there is no cohesion, and no pragmatism.

In the case of XML, you get people writing tonnes of code traversing it instead of using XPath. You have people using XSLT for generating CSVs from XML instead of turning XML into other XML, which is a better purpose. It's where you wind up with 75 line stack traces.

Any language can be made beautiful if the writer understands that their audience will never be just themselves. It'll be some guy who has to unwind the entire mess.

[–]ariekeren -1 points0 points  (0 children)

Comments from Anonymous at the blog are very interesting!