I found myself much in agreement with Ted Neward’s weblog piece on the downside of EJB. As an application developer, I have a strong negative reaction to anything that wants me to dump SQL and use some alternate layer. Perhaps for people who aren’t used to working with SQL, these abstraction layers are a good thing, but I know SQL, I like SQL, and I work with a DBA who’s a SQL master. To be honest, my job for the past three years or so has consisted almost entirely of writing web apps in Java, and I haven’t seen the need to learn EJB yet. I’m still waiting to be convinced. (I found this link over at Karl Martino‘s weblog.)
EJB dissent
I found myself much in agreement with Ted Neward’s weblog piece on the downside of EJB. As an application developer, I have a strong negative reaction to anything that wants me to dump SQL and use some alternate layer. Perhaps for people who aren’t used to working with SQL, these abstraction layers are a good thing, but I know SQL, I like SQL, and I work with a DBA who’s a SQL master. To be honest, my job for the past three years or so has consisted almost entirely of writing web apps in Java, and I haven’t seen the need to learn EJB yet. I’m still waiting to be convinced. (I found this link over at Karl Martino‘s weblog.)
Commentary
Previous post
Bush foreign policy visionNext post
Far be it from me to judge …