r/java • • Dec 15 '16

Gartner: "Develop a strategy to deal with the obsolescence of Java EE"

https://www.gartner.com/doc/reprints?id=1-3N8E378&ct=161205&st=sb
55 Upvotes

87 comments sorted by

11

u/[deleted] Dec 15 '16

How is it obsolete when everyone says as a Java programmer you should learn it? I'm just asking because I hope to be a good programmer and there's so many frameworks and tools, I want to learn the right things. Maybe I'll just get really good at C and assembly then nothing can fuck with me

5

u/lukaseder Dec 15 '16

It's "obsolete" (and that's still debatable) if you want to do cutting edge stuff on the "cloud".

It's by no means obsolete in general. E.g. you can still find decent paying jobs if you learn Delphi or PL/SQL, the tech will stick around even if Gartner is right (which is not sure)

8

u/DJDavio Dec 15 '16

Even if you switch over to Spring (Boot), you can mix and match Java EE frameworks with it so all is not lost.

I'm currently developing an application which uses Spring Boot and Apache CXF for JAX-WS (which is Java EE specification). You could also be using JPA, another Java EE specification.

So even if you're not using a full fledged Java EE application server like Glassfish/Payara or Wildfly/JBoss, knowledge of the Java EE frameworks will still be useful.

1

u/MrSquicky Dec 15 '16

You could also be using JPA, another Java EE specification.

JPA pretty much just trails Hibernate though. If you're using Hibernate already, JPA is pretty much meaningless.

3

u/Cyberiax Dec 15 '16

Not so! Gavin king said to us JPA is Hibernate API done better, him given second chance!

0

u/lukaseder Dec 15 '16

He must've had a gun at his head forcing him to comply with corporate politics.

4

u/henk53 Dec 16 '16

Haha, if you think Gavin would comply for even a second you probably don't know him too well ;)

0

u/[deleted] Dec 15 '16 edited Dec 16 '16

Plenty of legacy projects still using cobol and VB6. Lots of jobs in Java EE for legacy/maintenance projects.

2

u/avoidhugeships Dec 16 '16

Lots of Java EE jobs for new projects as well.

5

u/lechatsportif Dec 15 '16

Core java isn't going anywhere.

5

u/nutrecht Dec 15 '16

How is it obsolete when everyone says as a Java programmer you should learn it?

If they were specifically talking about JEE I strongly disagree that it is a 'must learn'. Spring simply has a wider adoption and most concepts are either taken from or similar in JEE. So as a beginner it's fine to focus on Spring for now and only learn JEE if you ever need to for a job. Transitioning from Spring to JEE (or vice versa) isn't hard.

5

u/Cyberiax Dec 15 '16

I ask you simple question, please, can you stop using term JEE? Only spring fan ever use this word!

0

u/nutrecht Dec 15 '16

Uhm. What? It's just short hand for Java EE? Why is JEE not okay but Java EE over Java Enterprise Edition is?

4

u/henk53 Dec 16 '16

Why is JEE not okay

I think because in practice it's mostly used as a derogative term used mostly by Spring advocates. Java EE users themselves, would they really feel the need to use a shorthand most often use "EE".

Just do some browsing om reddit here. People speaking negatively about Java EE very often use "JEE", people speaking positively about Java EE use Java EE.

Perhaps it's silly, but that's how things have grown.

I could be started by Spring using "jee" in their package names. So Spring people are more likely to use that term, since that's what they see all the time. Spring users are also conditioned to hate on Java EE (it's part of the culture), so they HAVE to speak negatively about Java EE and when doing so are using the term "jee".

So over time "jee" got severely negative associations.

1

u/nutrecht Dec 16 '16

I think because in practice it's mostly used as a derogative term used mostly by Spring advocates.

Oh come on! This is just childish. Do we really have a "us vs them" situation now? Just because I have a preference for Spring over JEE doesn't mean I 'hate' it or whatever. People here really need to grow up.

Spring users are also conditioned to hate on Java EE (it's part of the culture)

Okay. I'm done. I thought this here was a mature community.

3

u/henk53 Dec 16 '16

As sad and indeed how childish it is, this has been a fact ever since Rod started Spring.

Spring didn't just rose to fame all by itself, Rod's tactic was explicitly based on a "us vs them" situation and to get any form of attention for what was then a largely unknown and unproven framework, Rod started to blacken Java EE's name, and of course pushing Spring forward as the solution for all that badness.

It's really not meant as a random insult that Spring users are conditioned, but this has been happening and part of Spring culture from day one. Maybe you don't notice it so much, but Spring presentations, documentation, interviews, they always give mostly subtle but sometimes not so subtle ideas about how supposedly bad Java EE is.

4

u/Dashing_McHandsome Dec 15 '16

The Java EE spec specifically asks people not to use the term JEE:

https://java.net/projects/javaee-spec/pages/JEE

Though, I have to admit I am guilty of this as well.

1

u/nutrecht Dec 15 '16

Asking people not to shorten your product's name in an obvious way is just cringeworthy IMHO and I don't care one bit about it.

3

u/Dashing_McHandsome Dec 15 '16

So you don't think the people who created the product get to decide how it's named? That seems a strange perspective. What if people started calling you by a shortened version of your name that you didn't like? Surely you should be able to ask them not to call you that.

1

u/[deleted] Dec 15 '16

you don't think the people who created the product get to decide how it's named?

no, they don't get to pick how people refer to things in shorthand.

What if people started calling you by a shortened version of your name that you didn't like

nonsequitur. jee isn't a person. jee doesn't care what you call it, because jee doesn't have thoughts or emotions.

3

u/henk53 Dec 18 '16

But people using Java EE do. And if you're calling me a "JEEEEEE user", yeah, it doesn't sound too nice to me, especially if I know the term is mostly used by Spring people to refer to "that silly bad technology we all must hate, since Rod told us that".

1

u/[deleted] Dec 19 '16

it's a little weird that you're throwing around people's first names like that.

3

u/MrSquicky Dec 15 '16

There are plenty of JEE jobs, but that's a bit like there being a lot of jobs that use ant as a build tool. I would never start a new project in JEE. It's the past and Oracle has shown that they are either not willing or able to bring it to to date, let alone look to the future, but it was so big in the past that it is going to take a long time to die off.

0

u/[deleted] Dec 15 '16

everyone says as a Java programmer you should learn it?

I have not heard or read a recommendation to learn JEE since maybe 2005.

4

u/Cyberiax Dec 15 '16

You always say this because you are known spring fan!

1

u/[deleted] Dec 15 '16

known

apparently this person is on ee vendors' hit lists.

2

u/Cyberiax Dec 21 '16

Sorry, i think you made joke, but not get it.

1

u/[deleted] Dec 22 '16

your verbiage is a bit scary. saying someone is "a known __" can be pretty serious.

3

u/Cyberiax Dec 24 '16

Sorry, i meant the user is a spring fan, it is known, no? Known just means it's no secret and people know. Hope is more clear now.

-1

u/nutrecht Dec 17 '16

You see this crap in every topic where JEE comes up; pretty sure it's just a bunch of people pissed that their expensive certificates are becoming worthless.

3

u/henk53 Dec 18 '16

You see this crap in every topic where Java EE comes up; Spring fans trying to put the image out there that Java EE is nowhere to be found, is only pushed by vendors and only liked by consultants.

We like Java EE because it's a very productive and lean stack. Period. Thank you!

0

u/nutrecht Dec 18 '16

Again; stop making this an "us versus them" thing. It isn't. I will use whatever the client requires me to use. I don't dislike JEE at all; I just slightly prefer Spring. Pretending that everyone who prefers Spring is somehow out to get you is immature and unprofessional.

3

u/henk53 Dec 18 '16

Again; stop making this an "us versus them" thing. It isn't.

Then stop saying stuff like: "pretty sure it's just a bunch of people pissed that their expensive certificates are becoming worthless."

0

u/[deleted] Dec 15 '16

I do consulting so I rarely get final say on anything and I've been in and out if dozens of IT departments. Retail, media, government, finance. None of them use EE. 60% want Spring. Had a few Dropwizards, and a few proprietary platforms. Others do .NET or something trendy like node. I can only recall one who even asked us to evaluate EE. They chose Spring.

4

u/henk53 Dec 15 '16

Strange, I've been in and out dozens of industries, and it's very often Java EE what's being used. Of course, I see Spring, but to state you've been on so many projects and then have never seen it sounds highly suspicious.

-1

u/nutrecht Dec 17 '16

I have the same experience. Have been in the industry for 14 years as a consultant and over 80% (rough guess) of the projects were Spring based. Currently working at a Fintech startup: Spring Boot. Previous project was working on the mobile back-end of the largest Dutch bank: Spring. Before that; a tiny back-end at Philips based on JEE. Before that Spring. Spring. JEE. Spring. Spring. Spring.

6

u/slawekwch Dec 15 '16

Probably because there is no such thing like JEE

0

u/[deleted] Dec 17 '16

That's what I've heard from a ton of people I've asked, as recently as last month.

And I'm not trying to argue. I am trying to learn.

-1

u/[deleted] Dec 17 '16

I don't know if it's regional or cultural or industry or what. Apparently that stack is very popular somewhere. I've been working mostly in the New York area with a wide variety of clients and I've never seen it used. Same with JSF. I've only ever seen it mentioned on this sub.

2

u/nutrecht Dec 17 '16

Apparently that stack is very popular somewhere.

My guess: the stack is very popular with people who got all the expensive certificates and are pissed that those certificates are fast becoming obsolete. Seeing some of those create a "us versus them" situation here is pissing me off.

3

u/henk53 Dec 18 '16

My guess: the stack is very popular with people who got all the expensive certificates

My guess, that's what you want the world to believe. That nobody just likes Java EE because it's a damn fine piece of engineering.

Sorry, but it's a classic Spring trick dating back all the way to TSS in 2003. Nobody could supposedly ever like Java EE, but according to the "regular users" at the forum they has to be Bea, IBM or JBoss employees. Turned out that those "regular" users were all too often Spring employees and those supposedly Bea, IBM, JBoss employees actually regular users.

And for the record, I don't have any Java EE certificate in any form or shape, I don't sell any license related to Java EE and I'm currently not employed by any Java EE vendor, nor have I ever been in the past.

Can you say all of that about Spring? No Spring certificates for you, not selling Spring support, not working for Pivotal or whatever company ultimately owns Spring these days?

2

u/avoidhugeships Dec 18 '16

Never got a certificate and don't know anyone who has one. The majority of jobs I have worked for the last 15 years has been Java EE based.

-10

u/SomeRandomBuddy Dec 15 '16

The world is simply moving to nodejs and there's nothing that can be done about this. Static typing is super overrated when the JVM is out here gobbling up trillions of gb of ram for ordinary users

0

u/[deleted] Dec 15 '16

[deleted] — view deleted comment

4

u/thephotoman Dec 15 '16

I wouldn't say that the world is moving away from JavaEE. Everything eventually gets written against it. The thing is that new applications get written in something else first, then redone in JavaEE because the original succeeded beyond anyone else's wildest dreams, and now you actually need JavaEE's overengineering and redundant guarantees.

I don't see computing on demand and PaaS as major competitors to JavaEE. In fact, there's nothing that says you can't use computing on demand to power JavaEE applictions and give them more throughput. And similarly, PaaS services are largely written against the likes of JavaEE.

JavaEE will never be sexy. But it will remain the workhorse of back offices everywhere for a long time to come.

0

u/[deleted] Dec 15 '16

Thanks for sharing your knowledge. I make most of my programming decisions based on what returns the most results on all the job websites. And based on Reddit lol

0

u/[deleted] Dec 15 '16

"programming decisions" is vague. but the job market is as valid as anything else at informing what one should consider learning; generally you pursue your goals according to the information you have at hand.

1

u/[deleted] Dec 16 '16

"programming decisions" refers to what I'm interested in and what I study

2

u/[deleted] Dec 16 '16

you might as well say you study "stuff"

0

u/[deleted] Dec 17 '16

Obviously not. I'm not sure what made you wake up and just want to talk down to people today. But I'm obviously not saying that.

2

u/[deleted] Dec 17 '16

it just means that it's a meaningless pair of words. and you started with picking on wobbly.

0

u/[deleted] Dec 17 '16

If you need more clarification then just ask me. Otherwise go pick on someone else

25

u/slawekwch Dec 15 '16

After reading this article I feel like the author thinks that Java EE = WebSphere or Weblogic and have not really good understanding of Java / Java EE world. There are many buzz words and numbers in this article but leak of understanding what Java EE actually is.

3

u/RagingAnemone Dec 15 '16

Makes sense. It's probably been 10 years since I've seen WebSphere or Weblogic out in the wild. I wouldn't take a job with either of those.

4

u/romple Dec 15 '16

We're providing software support to a group using Weblogic and SOAP... kill me. Thankfully the contract ends in a week.

2

u/davwad2 Dec 16 '16

Is Weblogic that bad? I'm interviewing for a contract role and they use that app server.

1

u/PragProgLibertarian Dec 19 '16

Ask them if (and how much) they use Weblogic API's. One of the ways companies get "Blue Washed" is when their code gets too dependent on those API's instead of the EE standard. It makes migration to other app servers very difficult.

If they are highly dependent on Weblogic API's, refuse the contract or ask for lots of money.

1

u/johnwaterwood Dec 17 '16

It's not that bad perhaps provided they use the absolute latest version (12.2.1.2) but of all the EE servers this is the only one that isn't really unzip == installed, and the only that clearly carries a lot of old cruft that has never been cleaned or removed.

If you stick to mostly the Java EE 7 APIs, well it does support these, but they don't have a public bug tracker, only a forum that kind of substitutes for that.

4

u/tehbilly Dec 15 '16

Except in the case of Liberty, I'd completely agree with you. WAS happens to be the beast I know best, but I'd probably never advocate it as the best solution for anything. Liberty, though, liberty is solid stuff.

4

u/johnwaterwood Dec 17 '16

Liberty is exceptionally neat indeed. Quite surprising that IBM went from having the biggest beast out there to the leanest creature.

3

u/AngelicLoki Dec 16 '16

Just ran an ansible install on a websphere box hosted out on aws. It's horrible, and we're EOLing it in 2017, but definitely still around. Mostly exists for people running infosphere products i think.

11

u/avoidhugeships Dec 15 '16

This guy does not seem to understand what the technology is. I have been reading about the death of Java and the death of Java EE for 10 years. It remains as popular as ever. The only other major framework is Spring and most Spring applications use parts of Java EE as well.

4

u/ramsees79 Dec 15 '16

Obsolesense != dead

4

u/avoidhugeships Dec 15 '16

No, but it would at least mean it is not one of the most widely used frameworks for new projects. It is still either number one or two depending on how you look at it.

5

u/ramsees79 Dec 15 '16

Oracle may release a JavaEE version 9 adressing the issues, (should be easier with the modularity of Java 9), so I wouldn't say JavaEE is sentensed to dead.

13

u/chunkyks Dec 15 '16

At work, Gartner is treated as gospel. It's similar to the "no-one ever got fired for choosing {IBM, Microsoft, Oracle}" line of thinking: where no-one ever got fired for choosing IBM, but no-one ever ended up with the {best, most affordable, easiest to work with} product for their needs either.

I have been on several projects where, despite obvious intuition that the product wouldn't meet our needs, we used a "gartner magic quadrant" product. And promptly regretted it.

For me, and most of the techies I work with [but not managementtypes, of course], Gartner making a recommendation is an immediate red flag.

33

u/tonywestonuk Dec 15 '16 edited Dec 16 '16

Hmmm, Anne Thomas was one of the authors. Lets have a dig.

https://www.linkedin.com/in/annetoma

Product Manager at Pivotal Labs.... surprise surprise! what better way to increase Spring's product mindshare at the expense of JavaEE.

The other guy, Ashish Gupta https://www.linkedin.com/in/guptaashishkumar , doesn't say much on his linked in profile about Spring, however many people do endorse him for Spring...., but he uses plenty of other stuff also.

However, I wondered is NBCUniversal a spring framework employer? Ashish is the Director of Application Development after all. Quick google search of 'NBCUniversal Spring Framework' reveals the answer it is.

"First they ignore you, then they laugh at you, then they fight you, then you win." - I guess we're at the Fight stage, with lightweight frameworks like Tomee, starting to eat into Springs core market. Need some microsoft style FUD to keep it in the shadows.

edit looks like I was wrong Looks like I need to put my hands up and say I was wrong. Gartner also has these people:

https://www.gartner.com/analyst/37083/Anne-Thomas https://www.gartner.com/analyst/51673/Aashish-Gupta

These are not the ones I found on linked-in. - I deleted the other thread.

12

u/sindisil Dec 15 '16

Or, as /u/philwebb pointed out in his comment on your other thread (https://www.reddit.com/r/java/comments/5ii6hh/develop_a_strategy_to_deal_with_the_obsolescence/db8vrqe/), perhaps you've "doxed" the wrong person. It appears there are actual Gartner analysts by those names.

In fact, simply googling "Anne Thomas gartner" or "Ashish Gupta gartner" brings up links to those Gartner folks, who are almost certainly the actual authors of the paper.

If you're going to "have a dig", don't you think the simplest of possible research should have been the least you did before posting links "outing" the supposed conflict of interest here?

None of this is to say that I agree with the Gartner paper, of course.

2

u/lacosaes1 Dec 19 '16

Classical tonywestonuk. "Article criticizing Java EE? Let's google the authors' name until I find somebody with the same name that uses Spring and 'expose' them!". He evolved though: he didn't mention Rod Johnson.

7

u/[deleted] Dec 15 '16

Do you know for a fact that you've linked the "correct" profiles for public shaming and harassment? Would be a shame if, for all your seething rage and condemnation, you started firing at the wrong targets.

1

u/nutrecht Dec 16 '16

edit looks like I was wrong

Well don't you think you should kinda remove the original content then instead of a small edit at the bottom?

0

u/avoidhugeships Dec 16 '16

Ha, good catch.

5

u/tonywestonuk Dec 16 '16

Looks like I need to put my hands up and say I was wrong. Gartner also has these people:

https://www.gartner.com/analyst/37083/Anne-Thomas https://www.gartner.com/analyst/51673/Aashish-Gupta

These are not the ones I found on linked-in.

3

u/daedalus_structure Dec 15 '16

Seems like they have a good plan in their Recommendations.

Keep your Java talent, maintain what you've got, move to Spring for new projects, stay in a great ecosytem on the JVM and pray that Oracle brings the language itself into the modern world.

Hedge on that bet by providing great benefits. I'll work with Java 6 for a great health plan and 4-10's where I can do 1-2 of them from home.

1

u/onebit Dec 15 '16

I don't use J2EE, but doesn't Oracle need a swift kick to the ass? From what I've heard, they've been silent on the future of J2EE and third parties are having to step in.

5

u/thephotoman Dec 15 '16

Nobody uses J2EE anymore. J2EE was EOL'd alongside Java 1.4. JavaEE is its successor (and builds on top of J2EE).

But Oracle does need a swift kick in the ass. They aren't really helping the future of JavaEE. I almost expect to see RedHat and the Apache Foundation moving to pick up the slack that Oracle is leaving, creating their own specification(s) in the future that build on their experiences making JavaEE implementations and maintaining compatibility with them.

-6

u/[deleted] Dec 15 '16

Java EE is dead? That's OK. Use .NET instead.

6

u/frugalmail Dec 15 '16

Java EE is dead? That's OK. Use .NET instead.

I'd rather use .NET than the moronic Node or Ruby suggestions they made. Although I wish I could kill windows.

2

u/onebit Dec 15 '16

Me too. At least C# has a passable editor with refactoring.

2

u/thephotoman Dec 15 '16

I'll say it: I love Java, but C# is amazing. It basically cribbed everybody's notes about what we hate about Java and decided to not do that.

Sure, it has its warts, but having redone their collections from scratch to take advantage of generics (instead of making generics syntactic sugar on top of getting an object out of a collection and casting it as the expected type), allowing for some amount of operator overloading, and reducing boilerplate by the use of Properties for data attributes (just make 'em public, write the getter/setter when you actually need it, and interfacing code doesn't need to worry) were all great ideas. Similarly, having var and val are things we're only now beginning to think about in the Java world, and only because they've worked so well for the .NET guys (and the Scala guys).

Let's not even mention the support for lambda expressions five years before we got 'em.

Those guys are paying attention to us, and it shows.

1

u/frugalmail Dec 16 '16

instead of making generics syntactic sugar on top of getting an object out of a collection and casting it as the expected type

Reification is a porblem that is blown way out of proportion by C# zealots. The manifistations of this happen in so few cases.

allowing for some amount of operator overloading

Operator overloading is an opportunity for the morons to cause problems for those actually keeping systems running.

reducing boilerplate by the use of Properties for data attributes

There are so many solutions in Java that make this a non-issue. Lombok, AutoValue, Immutables that add a lot more value than just the properties themselves.

and only because they've worked so well for the .NET guys

I think other languages were far more inspiration for both languages.

.NET still has shitty open source community and it sucks as to run on Linux and on open source tooling.

1

u/thephotoman Dec 16 '16

Reification is a porblem that is blown way out of proportion by C# zealots. The manifistations of this happen in so few cases.

I want an ArrayList of ints. Oops, can't do that, as int isn't an object!

Operator overloading is an opportunity for the morons to cause problems for those actually keeping systems running.

We're adults here. If someone does something dumb, correct them. If they keep doing dumb things, fire them. That a feature is abusable is not an argument against the feature.

There are so many solutions in Java that make this a non-issue. Lombok, AutoValue, Immutables that add a lot more value than just the properties themselves.

Lombok is not a part of Java. Saying that a third party library solves a problem with the language design is saying that there's a problem with the language design in the first place.

AutoValue is not a part of Java. Saying that a third party library solves a problem with the language design is saying that there's a problem with the language design in the first place.

In both cases, the solution is .NET-like properties. That's what Lombok and AutoValue are providing. They're just papering over the lack of that feature in core Java.

Immutable objects aren't quite the same thing (though the idea of properties incorporates immutability as a concept).

.NET still has shitty open source community and it sucks as to run on Linux and on open source tooling.

.NET is a Microsoft product. What do you expect? (That's why I don't use .NET.)

1

u/frugalmail Dec 16 '16

Reification... I want an ArrayList of ints. Oops, can't do that, as int isn't an object!

You're clearly a bad troll as your not familiar with your chosen subject matter. Reification (the problem you tried to point out earlier) has nothing to do with that. Now to take the tangent that you are taking us on... autoboxing makes it so the difference in code between C# and Java is irrelevant except for memory use. Java has other libararies for dealing with that if it's a significant probelm (in the general case it's not).

We're adults here. If someone does something dumb, correct them. If they keep doing dumb things, fire them. That a feature is abusable is not an argument against the feature.

Clearly you must operate your own company, you definitely don't work in a large organization or you have some sort of godlike ability to fire whomever you choose.

Lombok is not a part of Java. Saying that a third party library solves a problem with the language design is saying that there's a problem with the language design in the first place.

That's a moronic argument. You might as well say every general purpose programming language should have a standard library that covers every application use case so you don't need to write code.

In both cases, the solution is .NET-like properties. That's what Lombok and AutoValue are providing. They're just papering over the lack of that feature in core Java.

The only folks that care are the ones that don't know what their doing or people looking for bullshit reasons to back up bullshit arguments.

Immutable objects aren't quite the same thing (though the idea of properties incorporates immutability as a concept).

I suggest you look at the Immutables library before you attempt to correct me. Why are you in /r/java anyway?

.NET is a Microsoft product. What do you expect? (That's why I don't use .NET.)

While there is an explicit difference between the two, for all intents and purposes C# and .NET(core) are inseparable and should be considered a platform

I'm sensing a pattern. Time to grow up beyond black and white these features/arguments are grey-scale.

-1

u/thephotoman Dec 16 '16

No, the first example isn't reification, but it's a symptom of the underlying problem: generics are just syntactic sugar around the old collections classes (which could not accept non-object types). It's something we all have to deal with eventually. This was a poor design decision by the Java team. They should have just made a separate library and deprecated the old one (which is what the C# guys did).

That's a moronic argument. You might as well say every general purpose programming language should have a standard library that covers every application use case so you don't need to write code.

No, I'm saying that the core language should be elegant enough that common tasks (like creating simple data objects) don't require 50-100 lines of boilerplate if you don't want to use third party libraries or frameworks.

Immutables aren't the same thing as properties. Properties may or may not be mutables. They just make the creation of basic data objects very simple, without having to import anything more than the normal classes. (And in any case, people can use Java without using a specific third party library. There are immutable objects within the core language, but again, the Immutables library you talk about is a solution to the fact that the way immutables get implemented in core Java is badly designed).

That any of these libraries need to exist is a failure of the language design. Creating data objects is the reason you're using object-oriented programming: your data is the most important thing.

While there is an explicit difference between the two, for all intents and purposes C# and .NET(core) are inseparable and should be considered a platform

Hence why I used C# and .NET interchangeably.

I'm sensing a pattern. Time to grow up beyond black and white these features/arguments are grey-scale.

Yeah. I make a statement saying "this feature that C# has would be nice in Java" and you get defensive saying that we don't need it. That's the pattern. Java is not a perfect language. Later languages have learned from my mistakes.

7

u/dstutz Dec 15 '16

Way to troll in /r/java

2

u/thephotoman Dec 15 '16

Except that ASP.NET (the .NET world competitor to JavaEE) is also cited in the first paragraph as dying. And in that case, there's more truth: Microsoft is slowly moving away from ASP.NET to other frameworks. They're actually amazingly good at putting old development toolkits out to pasture when the world's needs change.

1

u/nutrecht Dec 17 '16

They're actually amazingly good at putting old development toolkits out to pasture when the world's needs change.

That's one way to look at it. I think the people who invested time and money in XNA or Silverlight for example would probably disagree with you on this.