3 ms·
J2EE was awful because it was rushed; the early vision of Java was all applets, and when that didn't pan out, Sun was desperate to find a market, and settled on
by gaius 11y ago
J2EE was awful because it was rushed; the early vision of Java was all applets, and when that didn't pan out, Sun was desperate to find a market, and settled on Java as the new COBOL. Even now I'll wager 95% of what people use EJBs for they could do with POJOs.
- jrochkind1 11y agoThat is indeed what Eckel suggests in the OP, that it could have been a heck of a lot better if it hadn't been rushed for market penetration purposes. I don't know enough about the history of Java to say. But I know from my experience that good design takes time. And I agree with Eckel that a lot of historical Java API's aren't very good design.
- gaius 11y agoI was getting paid to write Java in 1995 so I saw all this first hand, but I got out of the Java game in the early '00s.
- reitanqild 11y agoEJBs are POJOs now :-) Source: I am a Java dev and I simply old code a lot by introducing EJBs.