"write a program that copies standard input to standard output":<p>org.apache.commons.io.IOUtils.copyLarge(System.in, System.out);<p>I despise the Java language as much as the next dev, and the core library is drastically underfeatured - But if you can't manage to copy one stream to another because you don't use libraries, you have no one to blame but yourself.
> So yes, I enjoyed programming in Java, and being relieved of the responsibility for producing a quality product. It was pleasant to not have to worry about whether I was doing a good job, or whether I might be writing something hard to understand or to maintain. The code was ridiculously verbose, of course, but that was not my fault. It was all out of my hands.<p>Yes, that's it, blame the language when you write poor quality software. If only I'd used language X instead of language Y, my code would've been easy to read, well-architected and thoroughly tested.<p>...and if language X in this instance is supposed to be Perl.... come on. It has built-in functions that change behaviour depending on whether or not you're assigning them to something.
What an utter load of crap. You can write excellent code in Java, you can write crap in Java. Due to its popularity, java has had everyone and their dog learning how to "code in java" and hence there are many poor "Java developers". That doesn't make it a bad language.<p>I quite like Java too, but without the mealy-mouthed backhanded compliments.