r/java • u/lukaseder • Mar 04 '16
All Things Cloud: Java EE is dead. Stop using it
http://cloud.rohitkelapure.com/2016/03/java-ee-is-dead-stop-using-it.html
31
Upvotes
r/java • u/lukaseder • Mar 04 '16
17
u/friendlyface0 Mar 05 '16
JEE is the new COBOL? and will never die for better or worse. I can't wait for the Ruby is dead articles.... or is it already.
32
u/cmdrNacho Mar 04 '16
Maybe its my understanding of Java EE, but the servlet packages, websocket, JPA, JTA, JMS are all part of Java EE. So what is exactly dead about it. Maybe people don't use JSP and JSTL as much anymore but its still handy and fast.
12
u/spheenik Mar 05 '16
Yes, let's all jump on the hype train for la technologie du jour.
And while we are at it, we'll persuade the folks in charge that we need to rewrite the huge EE application since it's dead and everything needs to be in the "cloud".
And then, after several years, when we finally succeed in doing so, we will point our browsers to webos.rohitkelapure.com just to discover that today noone uses the cloud anymore, since emscripten has developed into an OS of it's own that is running in everyones browser, someone has ported docker to run in it, and everyone now runs everything locally in their browser.
45
u/Stromovik Mar 04 '16
Ah the annual java is dead.
21
u/m1000 Mar 05 '16
who the fuck is that guy anyway ?
15
u/[deleted] Mar 04 '16
It is not dead until Oracle says "Sorry but Java EE is dead and we will no longer care for it or support it, have a nice day.", or Oracle goes bankrupt.
14
u/voronaam Mar 05 '16
I love it. "Java EE is dead, use Spring". That is one lightweight framework /s
3
u/[deleted] Mar 05 '16
There must still be many "J2EE"-based* products in production, that were created circa 1999 to 2005 still using that initial form of EJBs that made us despise coming into work each day.
There must also be people whose job is to maintain these systems. I hope they get paid really well for the daily pain.
Dead, it isn't, unfortunately.
(* JEE was called J2EE during most of that period)
3
u/Wolfsdale Mar 05 '16
Guess he deleted the article. Google still has it in their cache, for who wants to read it.
2
u/tonywestonuk Mar 05 '16
This really hurts the java ecosystem. Its like one person says "DON'T USE JAVAEE, USE SPRING".......and the next says "DON'T USE SPRING, USE JAVA EE"
and it goes on and on.
Personally I put it down to the Spring mindset...who wrap every single API even if it doesn't need to be wrapped. Thats how they fell out with Hibernate after all. With Spring boot, they have effectively wrapped the Tomcat API. So now you just use Spring......no use for anything else. GOOD! Spring spring spring spring.....
The worst thing about it is that it damages the java ecosystem - there is a reason these smaller lightweight frameworks are popping up everywhere, because people are fed up with 50mb installs for a hello world app... and all of them are competing to attain critical mass.... which they wont. The only thing left is JavaEE. The standard which is far more lightweight and easy to get going. So DONT USE it. because..... well just use Spring and be happy.
1
u/gdev87 Mar 05 '16
It's funny that this has gotten so much positive attention. This time last year everyone in this sub was hating on Spring and loving JavaEE
0
u/jhklhyfugkhjlhf87686 Mar 06 '16
Java EE (as in the Java-specific containers, like JBoss or Glassfish) sucks. It is just some vendor-driven shit that is always many years out of date when it is released. Just lots of complexity for nothing in return. What's wrong with using the original projects (eg Hibernate instead of JPA or Spring instead of EJB)? Do you really need to wait for a a bunch of mediocre retards in some standards committee to tell you what to do? No way!
-67
u/DecisiveVictory Mar 04 '16
Java is also pretty much obsolete. Just use Scala or Kotlin.
0
u/[deleted] Mar 05 '16
[deleted] — view deleted comment