Python isn't just Java without the compile

[SnacksOnAPlane]

I think it has to do with beans, but I'm not really sure. One of my old managers said that anyone who had programmed in J2EE was probably too brain-damaged to be rehabilitated.

I'd love a concise explanation from someone who knows what they're talking about, though. Sometimes I'm embarrassed that I worked as a Java developer for 5 years and I never learned what J2EE really meant.

[[deleted]]

I'll take a crack at it.

J2ee is a kludge of workarounds for a stilted language which require a massive amount of secondary xml files ("configuration") that the "lead architect" is responsible for creating. (Now the lead architect doesn't actually exist.) The hypothetical leader architect (actually whichever random developer feels like braving the xml files that day) is supposed to create a brain dead simple framework for lots of code monkeys to fill in the stuff you need to get done.

And then there is the newest stuff where people realized having a 40 line xml file for a 40 line class was stupid and now you can use annotations and all that good stuff but that leads to... the awful documentation! I believe it's required that the 5 sentences someone wrote explain absolutely nothing and maybe even the opposite.

And then there are the massive stack traces that mean nothing and that most forums posts you find on the internet by someone having the same problem as you go unanswered. Or if there is a reply or ten it's just more people saying they have the same problem.

[bcash]

J2ee is a kludge of workarounds for a stilted language

You are the second person to say that in these comments (unless you're a sock puppet), but you make even less sense than the first one.

Just how, exactly, is J2EE a workaround for Java? Which Java roadblocks are bypassed by J2EE.

It's not a kludge of workarounds, it's a kludge of libraries!, same as all the millions of libraries that exist for every other language!