3 ms·
i don't care what lipstick you put on that pig: when something as simple as writing to stdout requires that i first create a new class, i'm not interested. Edi
by thefastlane 11y ago
i don't care what lipstick you put on that pig: when something as simple as writing to stdout requires that i first create a new class, i'm not interested.
Edit: i do consider this a legitimate issue with how Java 'does' OO. i'd be curious to understand downvoters' thoughts.
One more edit: wow, tough crowd. for those not familiar, i'd suggest reading Steve Yegge's essay "Execution in the Kingdom of Nouns"
- Retra 11y agoIt's basically just a namespace for the function.
- cooper12 11y agoSystem.out.println("Foobar"); Either you're referring to something else or you misunderstood the language. The `out` stream is static so there is no need to create your own class first. (http://docs.oracle.com/javase/7/docs/api/java/lang/System.html#out http://docs.oracle.com/javase/7/docs/api/java/lang/System.ht...)
- umanwizard 11y agoYou're probably getting downvoted because it's factually not true. System.out.println("Hello, world!"); No new classes there.
- thefastlane 11y agohow would you compile that? here's what i get: test.java:1: error: class, interface, or enum expected System.out.println("foobar"); ^ 1 error
- umanwizard 11y agoOh -- you're talking about the fact that you need to create a new class for your program's main method? Yes, this is true, but it has nothing to do with printing to stdout. Edit: I don't like Java and I've read the essay you're referring to. Please don't assume bad faith in other commenters. Your original post was factually wrong. There's enough wrong with Java that you don't need to make stuff up to criticize it.