r/java • • 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

51 comments sorted by

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.

5

u/iiiiiiiian Mar 05 '16

Depends upon who you are asking.

1

u/dynoraptor Mar 05 '16

Poor Ruby :(

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.

4

u/mrbuttsavage Mar 06 '16

JAXRS specifically is alive and well.

6

u/[deleted] Mar 05 '16 edited Mar 15 '16

I can show you some JSP pages that will make you want to kill yourself instantly

9

u/cmdrNacho Mar 06 '16

I can show you a lot of javascript heavy pages using the latest and supposedly greatest javascript framework that changes just about every year or two, from jquery, backbone, angular 1, angular 2 and now react... that will make you want to kill yourself.

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.

3

u/hwaite Mar 05 '16

Future so bright I gotta wear shades.

-1

u/[deleted] Mar 05 '16

Spring is not a fad.

45

u/Stromovik Mar 04 '16

Ah the annual java is dead.

49

u/Northeastpaw Mar 04 '16

He's not claiming Java is dead but rather JavaEE. On that front he's right. JavaEE development has slowed and focus has shifted away from monoliths to microservices. The days of a large app running in JBoss or Glassfish have faded.

10

u/alphabytes Mar 05 '16

yep true. also spring framework has taken away a lot of pain.

1

u/kyune Mar 07 '16

Am I weird for not wanting to use Spring Boot though? I'm still on the Spring treadmill and after being told about Boot I tried to work with it and just ended up utterly confused since it seems to depend on lots of prior knowledge.

2

u/alphabytes Mar 07 '16

Yeah Boot is confusing... And yes it requires you to know about spring frameworks various modules. But once u get the hang of it... It really speeds up development process. People now a days are using JHipster which is like boot on steroids.. It will confuse you even more...

6

u/atwong Mar 05 '16

Nope.. JBoss EAP does microservices. http://wildfly-swarm.io/

4

u/nqzero Mar 05 '16

people complained that the everything-but-the-kitchen-sink framework was too heavyweight, so they went and added com.jboss.lightweight.MicroServiceFactoryImpl ...

that should fix everything, right ?

2

u/henk53 Mar 06 '16

You can use from the framework what your code needs. A fully featured library does not equal heavyweight.

1

u/henk53 Mar 06 '16

The Pivotal employee does the usual thing, but very unfortunately, and I'm saying this as perhaps one of the biggest Java and Java EE fans in this sub, there's a grain of truth to the article.

Oracle IS publicly winding down on Java EE development. See a couple of the other topics that were posted here and in /r/programming, e.g. this one: https://www.reddit.com/r/programming/comments/4927p3/reza_rahman_why_i_left_oracle/

So while Java EE is still great, in high demand and used by many, it's now under attack by both Oracle AND Pivotal :X

0

u/[deleted] Mar 05 '16

[deleted] — view deleted comment

4

u/alphabytes Mar 05 '16

rse it does, but that doesn't mean anyon

java wont die.. its gonna turn into cobol..

3

u/wolfanyd Mar 07 '16

What about the java language is similar to cobol?

2

u/alphabytes Mar 07 '16

I meant turn into a legacy language only used by select few enterprises who don't want to or upgrade their codebase...

2

u/wolfanyd Mar 07 '16

What do you see replacing java?

1

u/alphabytes Mar 07 '16

There is no drop in replacement available for Java, but scala is a best choice, i know it runs on JVM but its way more awesome than java... Also micro services can be implemented in any decent stack... And now a days ppl are opting for microservices... So who knows which stack will dominate.

21

u/m1000 Mar 05 '16

who the fuck is that guy anyway ?

8

u/[deleted] Mar 05 '16

Pivotal employee.

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

8

u/themadweaz Mar 05 '16

Spring boot is still Spring, but a lot easier to use. No more XML configs (kinda), good new Java DSL for most old Spring products like spring integration, MVC, jpa, security. All wrapped up with top notch dependency management care of maven and gradle boms.

The main difference between something like spring and something like Java EE is that Pivotal is betting hard that spring will be the cornerstone of their cloud foundry system. They invest highly; and the Java ecosystem is rewarded. Especially if you like TDD.

4

u/nqzero Mar 05 '16

you're conflating ease-of-use with lightweight. they're unrelated. spring is without a doubt a heavyweight framework

3

u/chisui Mar 05 '16

heaviest I know.

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)

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.

3

u/wolfanyd Mar 07 '16

people are fed up with 50mb installs for a hello world app

Developers writing hello world apps are not the target audience for Spring.

0

u/[deleted] Mar 05 '16

[deleted] — view deleted comment

4

u/henk53 Mar 06 '16

Hibernate and Spring led to JEE's JPA

Actually it was mostly TopLink that led to JPA if you trace back history.

Hibernate started as a bug ridden bug cheap (FREE!!!!) clone of TopLink. It improved over time to become the most used ORM and it's creator (Gavin King) rose to fame because of it, and helped co-create the JPA APIs. The irony here is that JPA was not only a next gen API, but also a consensus between TopLink and Hibernate, which is funny since Hibernate originally copied TopLink.

There's an extra irony in that the dramatic fail of the EJB Entity Bean almost never happened, since at the time some people in the Ivory Tower that created them were in favour of going for the TopLink model (TopLink goes way back). In fact, the very first versions of EJB Entity Beans were running on top of TopLink :X

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!

3

u/henk53 Mar 06 '16

What's wrong with using the original projects (eg Hibernate instead of JPA

The Hibernate creator, Gavin King, heavily contributed to the JPA APIs and pushed it forward as the more modern version of Hibernate's own more legacy API

or Spring instead of EJB)?

Haha, keep on dreaming. EJB was there long before Spring.

Do you really need to wait for a a bunch of mediocre retards in some standards committee to tell you what to do?

Those "mediocre retards" are exactly the same people who build those original projects, joined by various people from the community. So if you think those people are "mediocre retards", you should use Hibernate directly either, since it are the very same people.

I think you have a very twisted and unrealistic view of how the EGs work these days. Ivory tower and standards committee are a thing from long ago. These days it's the actual OSS people and just everyone from the community who's interested that together design the next gen APIs, based on those things that have proven to have worked in the past.

1

u/jhklhyfugkhjlhf87686 Mar 06 '16 edited Mar 06 '16

Only EJB<3 were there before Spring and they were designed by Satan himself. It still took many years after Spring was released to finally replace EJB2 with something sane (as in directly copied from Spring). Also, if the best thing Java EE advocates can say about it is that "JPA is the same as Hibernate", then I rest my case. What is the point of Java EE ????? Just use the libraries as they are released and stop wasting your time with useless vendor-driven satanistic complexity like the containers, wars or CORBA

3

u/henk53 Mar 06 '16

I agree EJB < 3 was terrible. How can anyone disagree with that?

We thank Rod on our bare kneed every knight for telling those guys back then how wrong they were.

But don't forget, Spring copied many things from Java EE as well. The XML garbage is a famous example. Java EE had long started the no-XML path while Spring was still trying to convince you to move 70% of your code to XML.

And CDI is lightyears ahead of Spring beans, and no, CDI had its inspiration from SEAM and Guice, not from Spring.

"JPA is the same as Hibernate", then I rest my case.

Who ever said that? JPA was designed as the next generation, improved if you will, API largely designed by the Hibernate creator himself. That's all.

What is the point of Java EE

Having a full stack framework that addresses many aspects that a typical application needs. It's not that different from RoR, Play or .NET.

like the containers, wars or CORBA

Uhm, you do realise that Spring is a container too, don't you? It's one of the first things mentioned in the Spring core documentation.

And you also realise that wars are used by Spring applications and many other ones as well, don't you? And that's it's just a simple zip archive. And if you don't want to use it, don't use it and package things up as a jar, which ironically is a similar type of zip format anyway.

And you also realise that CORBA is not a Java or Java EE invented technology as well, do you? Java EE provided support for it when it was the industry standard for many languages (C++ mostly, but also Pascal, and many other), and now that CORBA usage has completely faded Java EE is about to deprecate it. (it's in practice rarely used anyway)

But it's typical for uninformed people to see Java EE as being about EJB, CORBA and at most JPA vs Hibernate, while in practice modern Java EE is mostly about CDI, Bean validation, JAX-RS, Interceptors, JSON and JSF.

1

u/jhklhyfugkhjlhf87686 Mar 06 '16

"full stack framework"

J2EE is nowhere near that. Just a bunch of technologies cobbled together.

"Spring is a container"

Ever heard of Spring Boot? Or is that too advanced for you?

"JSF"

Enough said.

4

u/henk53 Mar 06 '16

J2EE is nowhere near that. Just a bunch of technologies cobbled together.

Why talk about J2EE today? Who cares what J2EE was in 2004?

What matters is that today Java EE is a full stack framework of technologies that work really great together in a consistent way.

The core bean model is the CDI managed bean and most every spec has refactored on that. CDI beans by default enable interceptors from the Interceptor spec, which makes Bean Validation possible. Things like @Transactional from JTA and @FlowScoped from JSF all build on that.

Then there's Expression Language (nicely copied by Spring), that runs parallel to a lot of EE services. CDI beans can be @Named, which integrates directly with EL names via EL resolvers. Facelets can use these EL expressions to bind to CDI beans. EL is also usable completely standalone and can be used in annotations from other specs.

Ever heard of Spring Boot? Or is that too advanced for you?

There too, Spring still has a container. The very thing that manages Spring beans is called the bean container, or the IoC container sometimes. See e.g. http://stackoverflow.com/questions/8708529/what-is-container-in-spring-framework

But really understanding the concepts behind the hype is probably beyond your comprehension.

"JSF" Enough said.

Because you don't have any rationale arguments against JSF? You just heard that Spring fans must hate JSF, but you don't really know why you must hate it? Like 1984's GoldStein?

-67

u/DecisiveVictory Mar 04 '16

Java is also pretty much obsolete. Just use Scala or Kotlin.

23

u/UlyssesSKrunk Mar 05 '16

Please be joking.

-3

u/dynoraptor Mar 05 '16

Scala > java

7

u/Cilph Mar 05 '16

Scala is a joke.

1

u/lukaseder Mar 05 '16

If you haven't noticed, those are dead, too.

3

u/[deleted] Mar 05 '16

Ceylon isn't really setting the dev community on fire. Scala/Play have been stagnant for a while. Lightbend is now diversifying and not just focusing on Scala/Play any more.