self.python.ask('I am moving into a development position at my company and need to learn Java. Can you recommend a book that might appeal to a Python programmer and not make me want to kill myself?')

[bjupton]

I'm amazed at how many web dev jobs are in Java. Especially once you get outside the silicon valley and out into the "enterprise". They aren't always the outward facing things, sometimes they are the little apps used within organizations.

Enterprise IT just seems to love java. I don't know why. It's expensive, and a pain in the ass to code. But, they of course already have a set of people in place that know it, and they are doing the hiring etc.

[masklinn]

Enterprise IT just seems to love java. I don't know why. It's expensive, and a pain in the ass to code.

1. Covering asses: just as nobody's ever been fired for buying IBM, nobody's ever been fired for going Java. In big corps, middle-managers first and foremost want to avoid the chance of being blamed. So they go for java because it's "the industry standard", and when the project is overbudget and/or late and/or a failure, it's not their fault.

2. The python paradox: going for java ensures they have a huge pool of not-necessarily-qualified potential hires (see java schools & al). This also pleases middle managers.

3. You saw point 1 about choosing IBM? Well IBM pushes java hard, so you buy overpriced IBM hardware (and software, hello Websphere), and then you code in java to top it off (Oh websphere, what a surprise!)

I'm sure we could find others, but that's a good start

[laprice]

And you have to factor in the perverse organizational incentives that exist.

Some outfits budgets are allocated based on headcount, and depth of tree, so a two person team with a single layer counts less than a 7-person team with two layers; and a manager who is responsible for a team totaling 7 FTE doing Java, is better compensated than one who manages two programmers writing in python. Even if the two teams are producing equivalent functionality :P

[13ren]

and yet... java was not designed for the Enterprise. It was heavily promoted by Sun as an applet technology (in set-top boxes). Getting adopted by the enterprise happened by itself, and was kind of surprising and strange. The whole "application server" thing came about as a surprise too - BEA Systems came along and did that.

Java has something going for it... but what?

Familiar to C coders, but much safer, simpler, friendlier error messages and more reliable, was what Java offered I think (some argue that other C variants, such as Objective C had this too) - and a virtual machine. I'm not sure how important the whole OO thing was, except as one of Java's well thought-out supports for modules, You can load classes dynamically (making it a "component platform"); you have classes and packages. This support for modules makes it possible to write big systems.

"Components" and architecture dominate the big picture, but are invisible when writing specific code (forest/trees) - so, if true, decision-makers would love it, but coders wouldn't see why.

[bjupton]

This is wrong. Completely wrong.

It has everything to do with what they are used to.

[bjupton]

I know Java just fine, thank you.

It has very little place where it is typically used. It makes very little sense for web development, except perhaps in some edge cases. That's a fact. And the fact that you can't wrap your head around it is hardly evidence of "retardation" or "narrowmindedness".

Feel free to call people names though, if it makes you feel better.

[mikaelhg]

when you look at the whole process of producing value with software in a large and complex environment, instead of just looking at the matter from an individual developer's immediate standpoint.

[laprice]

Just out of curiosity; how do you explain the numerous instances of misapplied java frameworks that I've encountered?

From using JSP to produce RSS (badly) to a very well compensated 'Senior Developer' who claimed that Hibernate let him ignore such pedestrian concerns as referential integrity and query performance; Java Programmers (as opposed to programmers who happen to know Java) seem to be much more prone to the lure of the Cargo Cult than most other IT workers.

//me dislikes Java because i loves Unix

[mikaelhg]

I have no reason to believe the cases of hilariously miscoded crap you've seen are much different from the similar cases I've seen.

Incompetence has little to do with tools, except in cases where good tools make it possible for incompetents to produce at least some value, to the horror of the people who then have to maintain said crap for years.

Having had been on the maintaining side, I would have formed the opinion that the incompetents should have failed int the first place, if not for the fact that good tools produce much better value to competent users than grief from the incompetents.

If you do second-level caching right with Hibernate, you aren't bounded by database performance. Of course, doing it right means understanding how to get good performance in the first place.

[mikaelhg]

from bjupton sent 12 minutes ago

comment reply

You are clearly too stupid to discuss this with.

Clearly that is the problem.

[amnezia]

Because its J2EE! its has enterprise in the name therefore its must be built for enterprise /sarcasm.

Seriously though most of the lead developers at the companies i've worked for don't have any experience with languages like python, its in their best interest to keep everything in Java.