12 engineers on Hacker News describe using Java EE first-hand: 2 endorse it, 4 regret it, 0 are mixed.
“The J2EE code was rock solid in reliability, including recovering from almost every kind of issue you can imagine over a decade”
endorse · production · 10 yr · hylaride · 2025-01-09 · source ↗ · wrong label?“I have written Java EE (and Jakarta EE) projects, and I found everything to be so much worse than e.g. Next.js + TypeScript.”
regret · production · super256 · 2022-12-20 · source ↗ · wrong label?“The largest madness was a J2EE mess where persistence was achieved by taking your current object, sending a message bean to the server”
regret · production · LanceH · 2018-11-14 · source ↗ · wrong label?“we've migrated a complex J2EE (with EJB 2.0 and such) E-Banking system to use only Jetty and JDBC directly.”
regret · production · lukaseder · 2014-11-27 · source ↗ · wrong label?“it's pretty great performance-wise and developers are kept fairly productive”
endorse · production · sgt · 2014-11-27 · source ↗ · wrong label?“Our application was meant to be 3-tier, but actually it's more like 10-tier.”
regret · production · ajuc · 2012-04-17 · source ↗ · wrong label?“We moved from 2-layer PL/SQL + C++ app to 3-layer PL/SQL + J2EE + SWT but on SWT there were like 5 additional layers”
neutral · production · ajuc · 2022-03-02 · source ↗ · wrong label?“Java with servlets, J++, J2EE, Struts, Seam, Spring, Struts2, SpringBoot”
neutral · personal · alasdair_ · 2020-05-16 · source ↗ · wrong label?“we introduced J2EE application server, exposed the database through hibernate”
neutral · production · ajuc · 2019-02-10 · source ↗ · wrong label?“I moved on to J2EE and Tomcat.”
neutral · production · williamcotton · 2014-12-17 · source ↗ · wrong label?“As late as 2010 I was working on a J2EE app trying to migrate it to Java 5.”
neutral · production · evilduck · 2013-10-10 · source ↗ · wrong label?“I tested Django, Rails, Cake, Java EE and buncha other stuff.”
neutral · personal · mahmud · 2011-11-16 · source ↗ · wrong label?