Why not use C then? Where do you draw the "it has to work" line?

axod · on Nov 10, 2009

You don't make sense again.

I do use C. For classes of problems that are appropriate - kernel/low level stuff.

For several things though, the lack of gc'd memory management, buffer overflows etc is a good reason not to use C.

It sounds like you truly identify yourself as a "<language> programmer" rather than a "programmer" :/

jrockway · on Nov 10, 2009

I am more interested in writing good programs than "just getting something done". That means using tools with the appropriate level of expressiveness, of which Java and C are neither.

Ask me which of Common Lisp, Haskell, and Perl I prefer, then call me a "<language> programmer". Remember, in the other threads, I am advocating combinations of features that do not currently exist in any programming language. I may be a "<language> programmer", I guess, but that <language> does not actually exist. Meta...

(You are the one who thinks that every feature that Java has is essential for programming, and every feature it's missing is <some cynical weasel-words here>. That is indicative of seeing the world through Java-colored glasses.)

axod · on Nov 10, 2009

FWIW, I've written far more non Java code than I've written Java code, so I wouldn't say I have "Java-colored glasses") ;)

I've also never said that Java is better than <insert other language here> without qualifying what it is better for.

jrockway · on Nov 10, 2009

When did you qualify what it is better for? (Better than what?)