August 19, 2006

Java—Second impressions

Now that I’ve had someone who actually knows Java teaching it to me, it’s time to re-think. Java is both not as bad, and much worse, then what I thought it would be.

I think I can happily keep churning out Java code as long as I’m going to get paid for it. The worst thing about Java is that it’s boring. Not challenging at all. Practically too easy, if you’re a patient man. Nothing exciting ever happens in Java-land. No cool shortcuts. And it’s way to verbose for my taste.

I understand why Java is so damn popular: it’s designed for enterprise use. I don’t think there’s any way possible to make generic enterprise applications interesting.

Working for a company—not that I’ve started work mind you—is damn impersonal. Everyone keeps talking about the necessities of good communication skills, team work and the such; but the work itself is not something you’d get attached to. Which strikes me as strange: I work best when I personally care about the results, not just for money.

“It’s business, not personal” is the worst thing anybody can say to me. Java seems to literally scream that out.

Still, not as bad as I thought it’d be.


No comments: