3 ms·

"write a program that copies standard input to standard output": org.apache.commons.io.IOUtils.copyLarge(System.in, System.out); I despise the Java language a

"write a program that copies standard input to standard output": org.apache.commons.io.IOUtils.copyLarge(System.in, System.out); 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.

zamalek 13y ago
> I despise the Java language as much as the next dev It's not so much the language that I despise - I never touched the language because of the end-user experience I got from installing the runtime: the nagging updates and the constant security headlines involving JVM. That's why I will never take the language (or the JVM languages) seriously: I simply would never put my users through what I am somewhat forced to go through (for the select few Java apps I do have to use).
- dkersten 13y ago
  I dislike java the language and java gui applications as much as everyone else, but I've never had any issues with the JVM for server applications.
- remon 13y ago
  And the prize for least informed opinion goes to... Let's review : 1) "I never touched the language" 2) Almost without exception Java vulnerabilities are related the the applet sandbox and not the core JVM Also, find me a single engineer how understands how the JVM works, what it does, how it does it and how it compares to alternatives that also thinks it's sub par software. I'll wait.
- EdwardDiego 13y ago
  I'd wager nearly all Java developers run their applications in their own JVMs, far far away from the sweaty mitts of client-side JREs. > That's why I will never take the language (or the JVM languages) seriously Seriously dude?
- theandrewbailey 13y ago
  Then you might think I'm the devil incarnate, because I force my blog visitors to use Java, because my blog is actually a Java Servlet app. Go ahead and try it: http://theandrewbailey.com/ http://theandrewbailey.com/ There's more to Java than the client runtime.
bulte-rs 13y ago
This seems to be a schism of some kind. Scenario 1: Ruby dev with problem while developing something in ruby: Ahh, There's a gem for that! Scenario 2: <other language> dev trying something in Java: Why isn't this in the stdlib? Sucks! Aergh. Bashing Java is just too easy; too bad it's actually a nice language.

zamalek 13y ago

> I despise the Java language as much as the next dev It's not so much the language that I despise - I never touched the language because of the end-user experience I got from installing the runtime: the nagging updates and the constant security headlines involving JVM. That's why I will never take the language (or the JVM languages) seriously: I simply would never put my users through what I am somewhat forced to go through (for the select few Java apps I do have to use).

dkersten 13y ago
I dislike java the language and java gui applications as much as everyone else, but I've never had any issues with the JVM for server applications.
remon 13y ago
And the prize for least informed opinion goes to... Let's review : 1) "I never touched the language" 2) Almost without exception Java vulnerabilities are related the the applet sandbox and not the core JVM Also, find me a single engineer how understands how the JVM works, what it does, how it does it and how it compares to alternatives that also thinks it's sub par software. I'll wait.
EdwardDiego 13y ago
I'd wager nearly all Java developers run their applications in their own JVMs, far far away from the sweaty mitts of client-side JREs. > That's why I will never take the language (or the JVM languages) seriously Seriously dude?
theandrewbailey 13y ago
Then you might think I'm the devil incarnate, because I force my blog visitors to use Java, because my blog is actually a Java Servlet app. Go ahead and try it: http://theandrewbailey.com/ http://theandrewbailey.com/ There's more to Java than the client runtime.

bulte-rs 13y ago

This seems to be a schism of some kind. Scenario 1: Ruby dev with problem while developing something in ruby: Ahh, There's a gem for that! Scenario 2: <other language> dev trying something in Java: Why isn't this in the stdlib? Sucks! Aergh. Bashing Java is just too easy; too bad it's actually a nice language.