3 ms·
> I was thrown at huge list of Java jargon, which I’ve never heard before. log4j, DI, IoC, RMI, JNDI, to name a few. ...and therein lies the problem. J2EE is t
by snorkel 17y ago
> I was thrown at huge list of Java jargon, which I’ve never heard before. log4j, DI, IoC, RMI, JNDI, to name a few.
...and therein lies the problem. J2EE is the umbrella word that covers up a rat's nest of API's that are constantly changing and being replaced in favor of other other API's.
What is so complicated about web development that Java developers feel that it requires 18 different layers of code and special servlet containers to accomplish? Take a peek at a plain Tomcat server process running absolutely nothing: it uses 430MB of RAM for one process, and that without any extra servlets installed. I'm convinced J2EE only exists only to keep mediocre developers employed at big companies that don't know any better.
- umjames 17y agoYes, you didn't know that? Wherever you see the word "enterprise" just replace it with "CYA". As someone whose day job entails writing servlets (and all Java web development boils down to servlets), I find that I really can no longer get excited about a Java web project because the first thing I think about is how much of a pain it's going to be to make it. Not pain as in difficult, but pain as in tedious.