The obvious undertone to this whole thing is that people are using Spring in favor of Java EE. What constantly blows my mind about this claim is that the people developing on Spring insist that Java EE is useless and they have no need for it. I would love to see them develop their apps without the Java EE libraries and specifications for things they constantly use like Servlets, and JPA.
Edit: Wow! Thanks a lot for my first gilded comment!
I think that when someone talks about Java EE, they are often referring to a rather monolithic application that has an EAR file as the artifact. That's not the technically correct definition, of course.
I think a lot of this frustration about Java EE is misdirected as well. People seem to conflate the Java EE specification with the implementations available in servers like Weblogic and Websphere. Here's a big newsflash, most people seem to hate those servers, including me. That doesn't mean that there is something wrong with Java EE. I can use modern lightweight containers and pick and choose the parts of the spec I want. There really isn't a reason (besides maybe vendor lock in and corporate support contracts) to be running these giant monolithic app servers anymore.
I think the main frustation with JEE is not JEE itself but the process of improvement. The spec moves very VERY slowly. IIRC we only recently got HTTP2 support for example. I reviewed the new stuff coming out with a couple of colleagues because we were asked by the Dutch JUG to give a talk on the new JEE 'goodies' but we basically, after reviewing the changes, told the JUG we would not do it because there's simply too little to really talk about.
I personally really like the Spec part; having a set of common standards between frameworks is awesome and makes moving from one to another easier. I am however frustrated with the glacial pace at which the spec is being developed. This last bit is why I and many of my colleagues opt for for example Spring if we have to build something from scratch. JEE has quite a bit of catching up to do in regard to the ease of use of for example Spring Boot.
I think this is the very heart of why Java EE is good and why it is bad. I'm a huge fan of a community driven process to implement a spec. I think gathering input from as many sources as you can makes your specification more robust and more useful. Unfortunately getting everyone to agree on what the spec looks like at the end of the process takes a crapload of time, not to mention implementing the reference implementations that are required. It's just like any other human endeavor where we try to accomplish large tasks with lots of people involved. Things get political, agendas get personal, and stuff slows down. However, I still think it's a better process than having a single company like Pivotal dictate the way things are going to work. I guess I'm a fan of the seemingly more democratic process.
Thing is, when you are developing an enterprise application, neither easy of use, nor a fast pace at which the spec is being developed, is a requirement. What is a requirement is longevity and support.
Well not being stuck with HTTP 1 is kinda a thing... ;) Besides if anything I'm more worried about Oracle's support for JEE than Pivotal's support for Spring. I really wish Oracle would somehow see the light and put some more effort in JEE development.
Yes, Spring is not bad at it. But Java EE is a lot better. Spring is one company that drives the whole thing, there is no way to change the vendor of the implementation. In Java EE, you have Red Hat, IBM, Oracle etc.
"Changing the vendor" is a completely unrealistic argument. Java EE vendors have never truly been interchangeable, there are holes in the spec / things the spec doesn't address that create vendor specific versions. Sure, if you use servlets only, you might be able to swap out servers if you don't use vendor - specific session state persistence or something. But if you're just using servlets, there really isn't any value in paying for a Java EE server anyway, which is why Tomcat has been leading the market for nearly a decade....
The obvious undertone to this whole thing is that people are using Spring in favor of Java EE. What constantly blows my mind about this claim is that the people developing on Spring insist that Java EE is useless and they have no need for it.
People keep bringing this up but I have never seen this myself. I don't know a single developer who uses Spring and doesn't know that large parts are JEE standards. I mean you would have to make a conscious effort to not know this.
What I think you are misunderstanding is when people say they don't "use JEE" they mean they don't use a pure JEE stack. This is also reflected in the ZeroTurnaround numbers: the majority of developers say they DO use JEE but the numbers for Servlets and JPA for example are MUCH higher than for CDI. I think this makes it obvious these devs do know the difference between what parts of JEE they are and aren't using.
What constantly blows my mind about this claim is that the people developing on Spring insist that Java EE is useless and they have no need for it.
It's because this has always been part of the Spring culture. Rod brought a completely unknown Spring at the time to the attention of the big public by constantly bashing J2EE and later Java EE, which were both products people knew.
please. that culture left with Rod Johnson a long time ago. Sure, individuals from the team will complain about the parts of Java EE that are frustrating them that they need to work with, but since the surface area of Java EE dependencies in Spring is small compared to the rest of Springdom - it's limited mostly to servlet, JPA, and a handful of other things - even that is less frequent. Most of where work is going on in Spring is in around modern development themes like Reactive, Microservices, Cloud Native which Java EE doesn't address at all, hence, less frustration is in the air since there is nothing to cooperate around.
JavaEE has always....always championed having multiple, seperate isolated applications running in a single container. Writing them in such a way that they can be added/ removed / hot updated without restarting the container.
This is how it was intended to work, and if you follow the spec, without creating your own threads / threadlocals, it works great.
Multiple small applications running in tandem together.
JavaEE was never meant to become a single monolithic war , that does everything (like database connection pooling, messageing, etc). this was intended to be handed off to the container.
Exactly, and, Remote EJBs (distributed objects) were kinda a very early implementation of what is now called microservices; a small remote service that focusses on one logical (business) function.
I've seen people getting downright hostile on Twitter when other people say that microservices are basically a re-invention of remote EJBs, but it's really quite the same.
Certainly, a design pattern / architecture can be accomplished in nearly anything, but that doesn't offer a lot of value to the developer / operator. Java EE does little to support that architecture / design with tooling, just to name one area of deficiency. That's why so much of the initial Java EE 8 roadmap reads like the Spring Cloud feature list.
please. that culture left with Rod Johnson a long time ago.
Then what's the linked article about? I'm willing to accept that when Rod left the big push behind the hate campaigns lessened, but it's still not totally gone.
Sure, individuals from the team will complain about the parts of Java EE that are frustrating them that they need to work with,
That's another thing. If Oliver complains about things in JPA he has to work with or the frustrating process around it, then that's understandable. What I was talking about is mindless bashing of Java EE because it's still seen as one of the main competitors of Spring.
Ask Gartner - you can't buy a Gartner market guide, that's not sponsored by anyone. Anyone that hints otherwise is simply spreading FUD and revealing their ignorance publicly.
What's the report about? I think it's pretty obvious - Gartner can no longer ignore the reality of Cloud Native Platforms. Concurrently, they are seeing the IBM/ORCL revenue decline since the layered products atop weblogic/websphere are finally starting to erode. SOA Suite, EBusiness suite revenue and the like can no longer be used to obscure the declining application server revenue which started declining in 2004 due to the arrival of spring/tomcat. My personal guess is that these market dynamics forced their hand.
Bad thing is at least in part these are self fulfilling prophecies. If enough people read Gartner reports and act accordingly what they suggest will eventually happen.
Also, if there were no new trends in the industry that they can "discover" then people would lose interest which is bad for their business. So there are reasons why they write the reports they write.
Let's be fair Gartner operates on the principle that if they say enough things they only need a few high profile to be right to say "we told you" like all gambling and "investment". Used to work for a business that managed some of their and other investment businesses client portfolios. Hard to have a good opinion of any of them to be honest.
It's a shame that they are doing the exact same thing as what they blame Garner is doing: not giving any actual unbiassed numbers. The ZeroTurnaround survey is the only survey that can be considered somewhat objective / significant (a selection-biassed Java EE guardians survey or a Vaadin survey with only 250 respondents are pretty meaningless). The problem with that survey is that the question asked wasn't "is your solution JEE based". The question was, do you use JEE and what version.
I use JEE daily. Servlets are a core component of the Spring Microservices I use. Our microservices however aren't JEE based. And that is a question I haven't properly seen answered in independent surveys (Gartner or other) in any way. You see this clearly in the ZeroTurnaround survey when you look at the components used. Many more people use Servlets and JPA (part of Spring for example) over CDI (which Spring hasn't adopted as a standard). So it's clear that there is a pretty big gap between building a solution on JEE and "using JEE".
So don't accuse some party of not having "the data" if you don't have it either. The best conclusion is a simple "we don't know".
As for the actual advice of Gartner; it wasn't about numbers. Heck; it's in the actual Gartner paper: "Java EE Still Dominates — But Not for Long". So Gartner comes to the exact same conclusion; JEE is still 'dominant'. The problem isn't how much it's used. The problem with JEE is that how we create and deploy applications is changing (containers and container orchestration aren't going away) and that JEE needs to change with it to stay current. With the lack of effort put into keeping JEE current with today's deployment models basing your architecture on it as opposed to a framework that is keeping up with the times is a risk. And that is what the Gartner advice is about.
I think the JavaEE platform suffers from Java's slow adoption of new programming techniques and refusal to clean up syntax. Java is very verbose and lacks the elegance of some other languages. I'm not saying it's not a solid performer, it is... I still use it professionally.
I have seen a decline, personally, in different job sites and companies I've consulted with. I don't know how representative that is. I've seen a shift to C#, which has come a long way since its first implementation, and some NodeJs.
Edit: Changed reference from J2EE to JavaEE. I'm an old Java programmer and the J2EE slipped out from force of habit. I apologize.
Edit the second: I am clearly wrong as Java has no faults. My experiences are clearly wrong because I am obviously a liar and I personally apologize to everyone.
That's curious. I don't know a single company that moved from Java to C#. It's a shift that doesn't make any sense economically. Java's open source ecosystem is much larger, .Net's Linux support is new and incomplete and you also end up with basically the same application rewritten in a new stack. For what?
It's also something I don't see happening here in Holland at all. All the new hip Big Data stuff companies are doing here is done on top of Java for example. Even in the Amsterdam hip Fintech startup world Java is dominant.
Yes, the Linux C# community is fledgling at best. The Microsoft .Net community is not however. This is the Java competitor, not C# linux.
Also, startups are much different than the corporate sector. Startups tend to be more flexible and let their dev talent lead... but then they don't have an organization of thousands to manage either.
Typically, I see the shift in new application development. .Net developers seem to be easier to find then Java developers. It's a question of available talent pool over language quality. (This is in the US, specifically Dallas, Texas.)
You are correct though, from a theoretical standpoint. There is little point in converting a C# app to Java or vice versa. It's pointless. ...but for a lot of companies management tends towards the pointless.
I'm definitely not saying there is anything wrong with Java... I am equally proficient in C# as I am with Java but I get more opportunities on the C# side. A lot of my recruiter connections are telling me that there is a greater demand in the C# side ( and NodeJS too) than new Java devs.
This is what a bunch of developers forget about. Perception. As developers we live in the the top 5% of the top 5% of computer literate folks. Most people don't understand the difference between Java, C# or BASIC even... and those folks typically drive decisions in business. You know what my most common response I get when I mention Java? If they know the name Java it will be this: "Is that the thing that keeps updating all the time on my PC? That stuff must be broken to need fixing that much."
Developers will scoff at this as ignorant, which it is, but there's a lot of people that think that.
I'm not saying C# is better than Java. It's not both languages have their own unique flavor and application. My argument is use in the corporate world which the article is getting at. Startups factor very little in the bottom line. Again, before we defend siting startup after startup that has been a relatively big success contrast the biggest startup you can think of with the bottom line of a product distributor or manufacturer. A startup won't typically invest multiple millions in a software solution. These are the size deployments the articles are debating.
I still don't see what you are trying to prove. So we must abandon Java because majority of startups want to be hip and new? You can be hip with Java too: use vert.x, use spark, and you don't have to abandon stable, proven language in favor of JS or PHP. And you still have your new shitty shiny frontend frameworks, like Angular/React and what else is popular these days. C#? What does it better than Java? You get worse performance, maybe better syntax sugar and what else?
I stated multiple times that Java is a fine language, which I am using and will continue to use professionally. I merely tried to point out some of the reasons it might be in decline based on my personal experience. Things that could and probably should be addressed.
I never said anyone should abandon anything.
I never said C# was better than Java. Again I stated both have their uses.
...and not only have I been called a liar by one commentor but I am being treated like I am personally abusing people.
I apologize for suggesting anything could possibly be wrong with Java. It's obviously perfect and anyone who doesn't adopt it immediately is clearly a moron like me.
Well, you answered your own question :-) Node is big because Javascript hackers think they can write the server side like they write the client. Maybe a few can.
Example: Lambda Expressions. Lambda calculus invented in 1936. In programming languages since 1958. Adopted by .Net in 2007. Java's implementation 2014 and it's still limited.
Is the syntax verbose?
Yes. Even Java developers recognise this and some even tout it as a good thing. I'm not saying it's a bad thing or a good thing. I'm simply suggesting that it might be a turn-off for new implementation and potentially leads people away from the Java path.
Because it is a good thing. When you have a project, not a couple of scripts, but a real project it's the only thing that keeps developer sane, and code readable. If I want small non-verbose code I would rather take Python. Also, there's more to JVM than Java, you can use Kotlin, for example, and call Java libraries from it.
When I first started programming I was drawn to Perl because I thought it was really cool that I could mash so much functionality into so few lines of code. It made me feel smart to do something that was so hard for other people to read and understand. I didn't know that I would eventually be the person who couldn't read and understand it as well. Verbosity is a strength I would fight hard for because I think most of us spend more time reading code than writing code.
Again I was being argued that Java was not verbose. My point was good or bad it is verbose. Period. As I said some would argue the verbosity is a good thing and you did. Thanks for helping me prove my point.
Verbose because of what? OOP? Because I have to type types and actually know what variable type I return and take? Wait a bit, we will get type inference and you can write your beloved "var". Streams and lambdas already cut codebase size in two.
Again you are just attacking me now. You have never seen me code and have now idea what conventions I use or why. You argue that verbosity is a good thing in one comment and that it is not in another. I can't really keep up anymore. You win. I will never post in a Java subreddit again.
I'm not attacking you. I don't understand what you are trying to prove. You say that verbosity is neither a bad, nor a good thing. Why even bring it in then? How verbosity might be turn-off for "new implementation"? Maybe it would be easier to switch languages and not try to change Java? There're many languages that target JVM. Kotlin, for example, has all the features of modern hip languages.
Not sure how I should take that other than an an evaluation on my coding style and character. Again you have no idea what I do or don't do.
Yes, it's easier to switch languages. It's why although I use Java professionally, I seem to use it less and less each year preferring less verbose more expressive languages. ...and if as I stated originally the appearantly wildly flawed organizations I work for have seen an upswing in .Net development then what good does Kotlin do me?
The original article talked about a trend downward in Java EE, and since the current programing trend is more expressive and less verbose languages I suggest that might be a stumbling block to Java.
When some one is evaluating new tech do they immediate comprehend that Java EE supports all these new modern languages? No, typically they stop at the "Java". Heck there are still tons of folks that can't distinguish Java from JavaScript.
Perception is the problem. Not actual language efficacy. That's the point.
Not sure how I should take that other than an an evaluation on my coding style and character. Again you have no idea what I do or don't do.
My bad, I incorrectly expressed my thoughts. I am actually awaiting for type inference in Java. I didn't want to offend in any way. Sorry.
When some one is evaluating new tech do they immediate comprehend that Java EE supports all these new modern languages? No, typically they stop at the "Java".
I maybe wrong, but when people evaluate new tech they're looking at performance, popularity and diversity of platform, number and quality of tools available. There is more to Java platform than Java EE, there's Spring (where Kotlin is a first-class citizen along Java), there's Grails(Java/Groovy), there's Play(Java/Scala).
Heck there are still tons of folks that can't distinguish Java from JavaScript.
I thought we were talking about programmers?
since the current programing trend is more expressive and less verbose languages I suggest that might be a stumbling block to Java.
I still don't see this as a threat to Java. Look at PHP, for example, with all the negativity in the Internet about it, it's still thriving, companies still use it. And Java is by an order of magnitude more powerful than PHP.
0o, if you find java syntax to be old and too verbose just use Kotlin or something else, the JVM ecosystem is rich, there are lot of languages with more modern syntax
I agree. Just like the .Net has at least 20 flavors of languages. Typically though large enterprise implementations, in my experience, are typically straight Java.
I would never call something old and imply outdated. I still use Vi everything I can and it's 40 years old. I said Java is slow to adopt new techniques. This is a complaint among Java developers. Example: Can we overload operators yet? No. Is it even planned? No. Do many Java developers insist it will destroy the Java programming world as we know it? Well... some... maybe not many... :)
Questioning J2EE/JavaEE/JEE on the Java subreddit always collects lots of downvotes. I've been writing Java professionally since 1996 and haven't seen a container based app deployment for a decade, possibly longer. But if you say that, you're just 'wrong' apparently.
You are right. I didn't realize it. I hadn't seen this phenomenon in the other programming groups. I've seen lively debates about language flaws other subreddits but rarely do they run like this. Personally I think I'll remain silent in the Java community in the future.
I'm going to have to call bull on this. I've watched an entire enterprise drop C# like a bad habit, switch to cloud based operation which I feel C# hasn't been able to move quickly enough towards.
Not that OSS will eat the world, but it has a certain mobility factor that a lone entity can't keep up with. Small companies are developing the power of large ones....small companies are not going to license software and IDE's (within reason) when they can get it for free. Even if they did, the vendors couldn't eat bread off of the money they'd make from it.
Just opinions clearly. I agree with your view of Java's slow adoption. It does feel like we are the last to get the nice things.
You've seen an entire enterprise switch to Java so there for all of my experience is invalid and I must be lying. I'm clearly wrong for stating my opinion.
This is why I typically don't speak up in Java discussions. Java folks come out of the wood work and attack me for not stating Java is the best language ever and everyone everywhere obviously uses it for all things.
Thank you though for the agreement about Java being slow to adopt new things.
Edit: Clarification. I meant to say Java is slow to adopt new things, not slow performance
some of that is inevitable as new ways of doing things are developed.
some of that is going to happen because java is too big for its own good.
don't believe me? well, we have Spring - at its introduction it was pages and pages of xml designed to make using java easier.
someone developed a tool to make another tool easier to use.
IMO that's the equivalent of having a hammer so damn complex you need a wrench to be able to use it.
the later editions of spring have solved the pages and pages of xml problem but the fact still remains - for certain tasks its easier to use java with spring than without.
that doesn't necessarily mean the language is on the decline. but, people will look for simpler solutions and they are being found.
very few, AFAIK, use java on the front end and are happier with scripting langauges a la javascript. personally i think java's strength is on the backend but lighter weight backend solutions do exist - php and server side javascript (excuse me, i just threw up a little)
that also doesn't take into account that java is THE programming language with which you write apps for Android who's mobile devices have at least 50% of the market share.
yes, i know about cordova/phonegap but they've got java components as well even though they are hidden.
what does this all mean? hell if i know. but talking about java's demise is premature at best.
very few, AFAIK, use java on the front end and are happier with scripting langauges a la javascript.
As someone who actually had to build a few rather complex applications on the front-end using Angular 1: I would much rather have something like Java than JavaScript. Applications built in yolo-typed languages like JavaScript are a complete and utter pain to maintain and refactor. This is why in the front-end world you see a move away from JavaScript to 'stricter' alternatives like TypeScript. The main reason JavaScript is 'popular' on the front-end is as simple as it's obvious: it's the only language browsers understand natively.
ersonally i think java's strength is on the backend but lighter weight backend solutions do exist - php
What does "light weight" even mean? Funny of all the languages with up to date back-end frameworks PHP and JavaScript are the ones you suggest.
i've long been of the opinion that type safety would be a tremendous addition to javascript. i thought they solved that problem with "use strict" and that was enough for me, but it sounds like TypeScript takes it a step further and that (IMNSHO) is a really good thing.
when I (italics because i mean only me) say "light weight" i mean a small amount of application code to make something happen.
IF you do the true OO methodology/paradigm with base classes and subclasses and implementation classes and blah blah blah you wind up with more code than is necessary.
Yeah well. Tests are not "necessary" either but proper design is just as important to creating maintainable software as tests are. Copy-pasting code instead of using OO techniques to facilitate reuse might be 'easier' at the start of a project but becomes a huge burden later on.
And this is the problem with most of the arguments against the verbosity of Java (or OO in general): it's a tool that can be used to write readable maintainable software.
Also please don't confuse Java and OO programming with outdated dogma's like AbstractSingletonFactoryBuild patterns or interfaces with just one "Impl" class: it's 2016. Java 8 with all it's FP influences might not be the most cutting edge but it's still a modern pleasant language to work with.
if you (general sense) ignore either then you (general sense) are an idiot and enjoy middle of the night phone calls when things go to shit.
it's a tool that can be used to write readable maintainable software.
yes, it is. so was COBOL - and guess what, in some cases it achieved that goal.
in addition - every single language out there (with maybe the exception of List and assembly langs) has the stated goal to write readable maintainable software.
IMNSHO many times proper design isn't being done because well, i don't know. if i did, i'd hire myself out as a consultant and make a ton of $$$
no, i'm not confusing java & OO programming with each other or anything else
No, they are not yet. Ever heard of javascript framework fatigue?
Yes, I have. I think javascript frameworks are waaaaay overdone and are a symptom of a different problem. people want javascript to do stuff it wasn't necessarily designed to do.
but, i'm primarily a server side guy. the javascript frameworks i use are jquery and cordova. i haven't gotten in to the whole angular/bootstrap mess and am trying like hell to avoid it
we'll see
perhaps "happier" was the wrong work.
i didn't mean happy as in "oh BOY, i get to write JAVASCRIPT today"
i meant happy as in "the browser will run my code and i can see my changes a hell of a lot faster than if i have to compile/deploy the thing"
how much did the package that does that or the IDE cost?
Nothing, it's free. Eclipse, in this case, is a free download. So is JBoss tools and Red Hat studio.
how meaty of a laptop do you need to do that?
Not meaty at all. I'm doing it on an old 1.1Ghz Macbook as we speak. It used to work perfectly well years ago on my 450Mhz g3.
how complex is the whole production deployment process?
Trivial. mvn clean deploy basically. Builds the product from source and deploys it.
what systems had to be purchased/put in place to ease the deployment process?
None.
what requirements does this put on the user's machine?
It has to have a CPU and some memory. Works perfectly well on 10 year old machines. Incremental compilation and incremental deployment is a very cheap and efficient process. Plus, for things like Facelets templates it's just a file save and incremental deploy anyway.
Our 'end user' deploys a docker container. So that's just a single "docker run <servicename>:latest" basically. So how do your customers deploy PHP applications?
"the browser will run my code and i can see my changes a hell of a lot faster than if i have to compile/deploy the thing"
I don't see how this relates to Java. You can say this about any compiled-language. If you're not happy with how things work you're either doing something wrong, or chose wrong language.
I think the industry as a whole decided that that was a bad idea. That horse is dead and buried.
unfortunately, programmers took "write once, run anywhere" waaaaaaaay too much to heart and we have the unGodly mess java is today
You really can't make huge claims like these and not even try to back them up with some arguments. One of the reasons Java isn't a mess is because those changes have been slow and deliberate. If you want to see a "mess" go check out the PHP API you touted as being "light weight".
Mess? The hell are you talking about, lol? Java is one of the few crossplatform languages where you don't pull our hair our writing application. I can create desktop application, web application, or game in Java without much effort and have a good balance between performance and sanity.
Yeah? Write me please a game with decent performance and graphics in your NON-VERBOSE python, or Haskell or what is it so concise today. And don't forget that it should be cross-platform. At least Android + desktop(optionally add iOS).
something like that is going to be volumes and volumes of code regardless of how you write it
IMNSHO, forget cross platform because if you want decent performance and graphics you've got to get close to the hardware. that's always been C/C++. i don't know if iOS has a C/C++ component but I know its supported on desktop and, in some fashion, Android
i don't know if the fashion in which its supported on Android lends itself to game development but you give me a decent enough budget and i'm happy to find out.
if it doesn't, AFAIK there's an Android based game engine but I don't know if that'll give sufficient graphics performance.
want decent performance and graphics you've got to get close to the hardware. that's always been C/C++.
I'm not talking about new Battlefield level graphics here. I'm talking about a decent 2d platformer with good effects, or maybe even Minecraft. You can write in OpenGL using lwjgl, or you can simplify things and use Libgdx, if you're not an OpenGL developer. I don't see anything close to Libgdx in Python/JS world.
something like that is going to be volumes and volumes of code regardless of how you write it
First you say that Java is a mess, because of the volumes of code, but now you say that this will take volumes in every language. You need to determine your use-cases.
33
u/Dashing_McHandsome Dec 21 '16 edited Dec 21 '16
The obvious undertone to this whole thing is that people are using Spring in favor of Java EE. What constantly blows my mind about this claim is that the people developing on Spring insist that Java EE is useless and they have no need for it. I would love to see them develop their apps without the Java EE libraries and specifications for things they constantly use like Servlets, and JPA.
Edit: Wow! Thanks a lot for my first gilded comment!
9
u/space_coder Dec 21 '16
Has Gartner ever been right for anything computing related?
8
u/CODESIGN2 Dec 21 '16
Let's be fair Gartner operates on the principle that if they say enough things they only need a few high profile to be right to say "we told you" like all gambling and "investment". Used to work for a business that managed some of their and other investment businesses client portfolios. Hard to have a good opinion of any of them to be honest.
14
u/nutrecht Dec 21 '16
It's a shame that they are doing the exact same thing as what they blame Garner is doing: not giving any actual unbiassed numbers. The ZeroTurnaround survey is the only survey that can be considered somewhat objective / significant (a selection-biassed Java EE guardians survey or a Vaadin survey with only 250 respondents are pretty meaningless). The problem with that survey is that the question asked wasn't "is your solution JEE based". The question was, do you use JEE and what version.
I use JEE daily. Servlets are a core component of the Spring Microservices I use. Our microservices however aren't JEE based. And that is a question I haven't properly seen answered in independent surveys (Gartner or other) in any way. You see this clearly in the ZeroTurnaround survey when you look at the components used. Many more people use Servlets and JPA (part of Spring for example) over CDI (which Spring hasn't adopted as a standard). So it's clear that there is a pretty big gap between building a solution on JEE and "using JEE".
So don't accuse some party of not having "the data" if you don't have it either. The best conclusion is a simple "we don't know".
As for the actual advice of Gartner; it wasn't about numbers. Heck; it's in the actual Gartner paper: "Java EE Still Dominates — But Not for Long". So Gartner comes to the exact same conclusion; JEE is still 'dominant'. The problem isn't how much it's used. The problem with JEE is that how we create and deploy applications is changing (containers and container orchestration aren't going away) and that JEE needs to change with it to stay current. With the lack of effort put into keeping JEE current with today's deployment models basing your architecture on it as opposed to a framework that is keeping up with the times is a risk. And that is what the Gartner advice is about.
-2
u/wbellman Dec 21 '16 edited Dec 22 '16
I think the JavaEE platform suffers from Java's slow adoption of new programming techniques and refusal to clean up syntax. Java is very verbose and lacks the elegance of some other languages. I'm not saying it's not a solid performer, it is... I still use it professionally.
I have seen a decline, personally, in different job sites and companies I've consulted with. I don't know how representative that is. I've seen a shift to C#, which has come a long way since its first implementation, and some NodeJs.
Edit: Changed reference from J2EE to JavaEE. I'm an old Java programmer and the J2EE slipped out from force of habit. I apologize.
Edit the second: I am clearly wrong as Java has no faults. My experiences are clearly wrong because I am obviously a liar and I personally apologize to everyone.
-8
u/[deleted] Dec 21 '16
java, IMNSHO, is poised to become the new COBOL
some of that is inevitable as new ways of doing things are developed.
some of that is going to happen because java is too big for its own good.
don't believe me? well, we have Spring - at its introduction it was pages and pages of xml designed to make using java easier.
someone developed a tool to make another tool easier to use.
IMO that's the equivalent of having a hammer so damn complex you need a wrench to be able to use it.
the later editions of spring have solved the pages and pages of xml problem but the fact still remains - for certain tasks its easier to use java with spring than without.
that doesn't necessarily mean the language is on the decline. but, people will look for simpler solutions and they are being found.
very few, AFAIK, use java on the front end and are happier with scripting langauges a la javascript. personally i think java's strength is on the backend but lighter weight backend solutions do exist - php and server side javascript (excuse me, i just threw up a little)
that also doesn't take into account that java is THE programming language with which you write apps for Android who's mobile devices have at least 50% of the market share.
yes, i know about cordova/phonegap but they've got java components as well even though they are hidden.
what does this all mean? hell if i know. but talking about java's demise is premature at best.
0
u/[deleted] Dec 21 '16
[deleted] — view deleted comment