Skip to main content

Which Java platform are you personally most interested in?

Java Enterprise Edition (EE)
35% (360 votes)
Java Standard Edition (SE)
54% (558 votes)
Java Micro Edition (ME)
10% (104 votes)
Java Card
0% (4 votes)
Something else
1% (13 votes)
Total votes: 1039

Comments

EE has no "home use" value

When I code for myself (projects, shareware etc.) I don't need any EE features. I actually found it difficult to get into EE, which I need and use a lot at work, because I won't/don't play with it at home - I don't need any beans, transactions, security etc. for writing hobby applications.

SE vs EE

To me SE is more important, because without SE there is no EE.

Okay I know, not terribly profound or anything like that. EE concerns me because it is 'faddish'. When EE was being put together Corba looked like 'the next big thing', so instead of RMI we ended up with RMI over Corba, even though Corba was more limited than RMI and so the combination of the two is weaker than RMI on its own.

We see similar things in the EJB/persistence and web framework worlds. People want their favourite framework to become the standard at the expense of everyone else. And then we start having integration problems ...

And the (easy) way to solve those problems is just to shove everything into XML config and let the poor SOBS on the receiving end sort it out. In many ways XML is becoming the underpinning of EE rather than Java, and thats not a good thing.

As a Java developer I worry that we have become enamoured of our own cleverness and forsaken Java's ease of use.